Reputation: 1672
Using "Configure run after" to handle errors thrown by flow action is a well-known pattern.
But what about a trigger that has failed? Is there a way to configure the flow to, say, send a message, when an error occurs in a trigger?
For example, my flow is triggered when an item is created or modified on a SharePoint list and if someone deletes this list I will never know that something is wrong until I browse the flow trigger history and see "list not found" trigger error. However, it won't even appear in runs history because the flow won't start any action, so I guess "Configure run after" is useless in such case? Any other options?
Upvotes: 0
Views: 332
Reputation: 60841
Upvotes: 0