Share
ReportHello,
I have error handling set up with all of my flows. Typically, it works the way I would expect. But a recent error has me troubled. Hopefully this makes some sense...
A high-level view of the error is below (I am guessing my Scope was "skipped" because of the terminate?). It is rare that error handler at the end of my Flows (Scope - Flow Fail) is ever used as I have a few error handlers before it. It's really just there to catch anomalies.
Looking inside the Condition that had the failure, we can see where the issue started:
I am not 100% sure why there was an issue with the "Create File" step, but that isn't the real issue I have here...
At the very end of these failed processes there is a branched section:
The left side (Approval) has my main error handling step for this section (the "Reminder" on the right branch is new. This part used to be linear). And the very last step is my "Delete item" step that removes this flow's trigger (this flow is triggered by an item being added to a SP list - as long as the item is there, this flow will catch it and continue trying to run).
This all brings me to my two questions:
- Why didn't my error handler (Scope - Fail) in the "Approval" branch catch this error? Was it because it was inside a branch? Instead, it passed to the error handler outside the Condition. I just modified the flow to add a duplicate error handler just before the branch, in case that has something to do with it; and
- Most importantly, the trigger item for this flow is missing from my SP list, but the action "Delete item - S123 Router" never triggered. Can you think of any reason why this item would be deleted from a SP list on a failed flow run?
Thank you.
All responses (
Answers (
535
