The flow engine is not processing the Updates faster and which results in the delay of updates to the Major Incidents.. In the processing duration for the events in event queue for few incident records. It took so long for processing the updates from flow designer. It’s not expected behavior usually the updates would happen no longer than 60secs.

When it is happening:

It is happening occasionally where the event processor is busy and once the event queue is cleared , the updates are happening to the Incidents.


To run the Flow synchronously for the flow that you have configured on MIM incidents.

Release or Environment



Configuration of "When to run the flow"


The Flow engine can be run synchronously by changing the "When to run the flow" to "Run flow in foreground".

Option Description in the product document :

Run flow in background (default) Flow that runs asynchronously in the background. Use this option for flows that do not require immediate updates and to allow other system processes to run at the same time.

Run flow in foreground Flow that runs synchronously in the current session. Use this option to provide immediate updates to an end user. For example, if a flow opens a task after the previous task closes, use this option to open the next task immediately after a user closes one.
Note: Running a flow in foreground blocks the current session thread and prevents it from running anything else until the flow finishes. To avoid making your system unresponsive while running a flow, do not use this trigger option for flows that take a long time to complete.

Additional Information

Refer the below Flow Designer Document regarding the triggering options.


Article Information

Last Updated:2020-03-26 01:09:10