Periodically, I've come across running flows that have been running in-progress for many hours when they normally take just a few minutes. The job is "stuck" in in-progress and only partially completed. Usually, this condition is noticed by users that are missing critical data and often many hours later. I've seen this cause late shipments and other detrimental consequences.
Of course, jobs should never get stuck like this, but I've seen it happen about 6 times a year among my clients.
I'm would like to be able to setup a timeout value at the flow level. If an instance of the flow runs for more than the set time (in minutes) then then an error is created and optionally the flow automatically cancelled.
Please sign in to leave a comment.