Suppress message that system flow is still running

  • 22 March 2023
  • 2 replies

Userlevel 5
Badge +5

We have a system flow that runs every minute. Most of the time it does not do anything. However sometimes it does quite a lot. This process takes up to more than a few minutes. This is aboslutely no problem. Except that this makes the indicium log file flood itself with ‘procsess still running’ exceptions.  

How can we get indicium not to report this? 

2023-03-22T11:38:00.3653547+01:00  [ERR] Error scheduling system flow '"flow_export_message"' for application 35. (b95a9b29)
System.Exception: An exception occurred while trying to log the start of the system flow.
---> Microsoft.Data.SqlClient.SqlException (0x80131904): <msg id="system_flow_still_running"></msg>
at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
at Microsoft.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader(Boolean isInternal, Boolean forDescribeParameterEncryption)
at Microsoft.Data.SqlClient.SqlCommand.InternalEndExecuteNonQuery(IAsyncResult asyncResult, Boolean isInternal, String endMethod)
at Microsoft.Data.SqlClient.SqlCommand.EndExecuteNonQueryInternal(IAsyncResult asyncResult)
at Microsoft.Data.SqlClient.SqlCommand.EndExecuteNonQueryAsync(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location ---
at Indicium.BackgroundServices.SystemFlowScheduler.<>c__DisplayClass21_0.<<runSystemFlow>b__0>d.MoveNext() in C:\azp\agent\_work\1\s\src\Indicium\BackgroundServices\SystemFlowScheduler.cs:line 191
--- End of stack trace from previous location ---
at Indicium.BackgroundServices.SystemFlowScheduler.withLogging(String logMessage, Func`1 task) in C:\azp\agent\_work\1\s\src\Indicium\BackgroundServices\SystemFlowScheduler.cs:line 293



Best answer by Vincent Doppenberg 22 March 2023, 11:53

View original

This topic has been closed for comments

2 replies

Userlevel 6
Badge +4

Hello Kasper,

This issue should only be present in version 2023.1.13.0 of Indicium. It was resolved in 2023.1.13.1 onwards. Can you check your version of Indicium?

Userlevel 5
Badge +5

Check, we indeed used 13.0, in the latest version this indeed seems to be solved, thanks!