Skip to main content

Sometimes you would like to abort a system flow. A reason for this could be that by mistake a never ending loop has been created. Or that a system flow is simple stuck, running and ran into an error but did not stop, preventing the next scheduled time to start the flow.

Currently the only way to resolve both cases is by restarting indicium (application pool recycle or webserver restart). This is not really what you want. Because if this occurs in the production environment, this will result in every user getting logged out.

Therefor it would be great to have an option to abort a system flow. This option should be available in IAM on the scheduled system flow screen. But also in the process flow monitor, allowing a user to abort a flow during a test or manual run.

The expected behavior would be that the system flow will execute its current flow action and after doing so, will simply stop. And if it is not executing a flow action at all, stop as well.

Great idea! I recognize the issue and have thought about it myself as well. Having the ability to manually abort a system flow would be helpful.

In addition, I think it would be valuable to have an option within a process flow to set a maximum number of iterations or actions. This could serve as a safeguard against infinite loops or unexpectedly long-running processes. By setting limits in advance, the system can automatically protect itself from getting stuck, without requiring manual intervention. The user should also receive a notification when the configured maximum number of actions has been reached, so they are aware that the flow was stopped intentionally as a safety measure.