Flow Execution MutexesIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } A mutex is taken against sys_flow_context for every non-Quick flow execution and against a Quick (Quick API) context ID for quick flows. When a flow step execution time exceeds the value of the property set in 'com.glide.hub.flow_engine.mutex_expiration', this mutex will be expire, and the flow will be restarted from the last quiescence point. Quiescence point are points where a flow goes in to a waiting state. Common actions such as 'Wait for Duration', 'Wait for Condition' or 'Ask for Approval' can cause a flow quiesce. On mutex expiration, node logs with below message can be observed: WARNING *** WARNING *** Not releasing expired mutex sys_flow_context_mutex_{flow_context_id} System properties 'com.glide.hub.flow_engine.mutex_expiration' By default, system property 'com.glide.hub.flow_engine.mutex_expiration' is not visible on the 'sys_properties' tables. The default value of this system property by release version is as below: Vancouver - 900 secondsWashington DC - 3600 seconds *Default value in Washington DC has been increased to 3600 seconds from 900 seconds. To override the default value, create 'com.glide.hub.flow_engine.mutex_expiration' can be created on the 'sys_properties' tables, and the value can be edited accordingly. FAQ 1. Is there any potential negative effect of extending the system property com.glide.hub.flow_engine.mutex_expiration to a large value?There should not be any significant issues related to extending this value. 2. Are there any other measures that can be taken to avoid mutex expiration?It is generally not recommended to have long-running flows. Instead, it is advised to break flows into smaller, reusable components. For further information, refer to the relevant documentation. 3. Is the time configured in com.glide.hub.flow_engine.mutex_expiration based on the time when the flow starts or the last quiescence point?The expiration time is measured from when the mutex is acquired, which typically corresponds to the flow start or when it resumes from a quiescence point. Example:If a flow includes an "Ask For Approval" action, the mutex expiration time is calculated from when the approval action is completed, rather than from the flow’s initial start. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When a flow is being affected by mutex expiration, consider the following actions: 1. Changing the default value of system property 'com.glide.hub.flow_engine.mutex_expiration' to ensure mutex does not expire. 2. Review the flow itself to cut down on the flow run times. Check the 'Design considerations for Flow Designer' documentation for details on best design practices.Design Considerations for Flow Designer