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.
