+13Since the new version the generation process is done by Indicium. However, often this message is displayed;
It usually disappears/appears a few times and the generation does not fail, but still, It does not look good to me.
What is the cause of this message?
Thanks!
Best answer by pauloportu
after checking our logs we found the following:
2021-12-13T14:27:30.0377288+01:00 [ERR] Error scheduling system flow 'system_flow_agent_check_in' for application 14. (34d69cfe)
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.SystemFlowSchedulerBase.RunSystemFlow(Int32 guiApplID, TSFApplication application, FullProcessFlow systemFlow, DateTime scheduledTime) in C:\azp\agent\_work\1\s\src\Indicium\BackgroundServices\SystemFlowSchedulerBase.cs:line 112
at Indicium.BackgroundServices.SystemFlowScheduler.RunSystemFlow(Int32 guiApplID, TSFApplication application, FullProcessFlow systemFlow, DateTime scheduledTime) in C:\azp\agent\_work\1\s\src\Indicium\BackgroundServices\SystemFlowScheduler.cs:line 90
at Indicium.BackgroundServices.SystemFlowSchedulerBase.ScheduleSystemFlow(Int32 guiApplID, String systemFlowID, DateTime scheduledTime) in C:\azp\agent\_work\1\s\src\Indicium\BackgroundServices\SystemFlowSchedulerBase.cs:line 84
ClientConnectionId:5f93a48f-65ed-41ac-a260-7e708c204d01
Error Number:50000,State:10,Class:16
------------
maybe some recognizes this error? Or maybe TW team can work with the info.
thank you,
Paul
+23When going into IAM, navigate to Applications, select the SF application, navigate to detail tab Scheduled system flows. In here, the system flow "system_flow_agent_check_in” is the one I'm interested in. It should have a log record every 30 seconds like this; is that also the case for you both or is it different?:
(Ignore the new available Task, that's 2022.1 functionality 
)
+12
+16Hi,
This message is given when Indicium does not pick up new system flows for at least 61 seconds. This usually means that Indicium is not running anymore and should be reactivated.
Hi
How can we tweak this setting. My partner here in Brazil encounters this message more than I do. How does it exactly work? We have the Indicium running in the cloud. When he gets the message more than I , does this directly relate to internet speeds? And is there a way to tweak with settings?
Because I have been monitoring the Indicium and it hasn't gone offline yet, but still we receive these messages that: 'we stopped hearing from Indicium'.
+23Hi,
This message is given when Indicium does not pick up new system flows for at least 61 seconds. This usually means that Indicium is not running anymore and should be reactivated.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.