Share
Report
16I have a flow that uses Microsoft Forms as a trigger. The flow is about sending an email when meeting certain conditions and then saving the form submission in a Sharepoint list. The whole flow usually only takes 2-4 seconds when ran successfully. However, due to a large amount of users submitting a form recently (especially at the start of office hours), some flow runs become stuck at a step that doesn't usually take time to finish (initialize variable, compose, etc.). The flow run is still said to be "Running" when viewing in the run history. When "Running" flows reaches a certain number, the flow now won't run the next form submissions. This flow works perfectly fine at the rest of the time aside from the start of office hours.
This is the usual look on how it becomes stuck at "Running".
One workaround that I have done to prevent the flow from running for a long time is to set a parallel delay timer at the start and automatically terminate the flow if it reaches X seconds to finish (as seen above). However, the flow sometimes also gets stuck at the delay part, running for more than the set X seconds and not proceeding to terminate the flow. I have also done setting different degrees of parallelism on the concurrency of the flow trigger, but still having the same problem.
My solution for this is manually cancelling the "Running" flow runs and resubmitting them one by one during office hours. I know this is an issue on Automate's processing capabilities, but is there any way to automatically cancel these long running runs and still allow other succeeding flow runs to run without being stuck? It's fine to have failed runs, just as long as the runs don't get stuck.
Thanks. -Ryu
All responses (
Answers (
