Customers may see the following banner in a flow's run history.
[Asset 4540230]
Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.
View products that this article applies to.
Customers may see the following banner in a flow's run history.
[Asset 4540230]
The banner is displayed when the flow’s trigger encounters an error. The purpose of the banner is to inform the user of a problematic trigger which will result in a flow not running. The banner can be particularly helpful when a flow has not had an initial run and therefore will have no run history available.
To understand why the trigger failed and how to fix the issue:
1. Click the “Fix the trigger” link.
2. The failed trigger will be displayed. Click the trigger to inspect the underlying error message:
[Asset 4540233]
In the above example, the trigger failed because the specified folder was not found in the SharePoint library. The fix would be to update the folder name to a valid name.
Trigger failures with 4xx status codes are typically errors that the user should fix. Common issues might include:
· A change in the connection that the flow is using (e.g. password expired)
· A trigger input that is invalid
· Failure to register a webhook trigger
Trigger failures with 5xx status codes are typically system issues and can occur due to transient events. These errors should eventually self-heal.
Currently the banner may continue to be displayed even when the next trigger event is successfully executed. The product team is working toward resolving the issue. If your flow continues to run successfully even while the banner is present, then you may be encountering this issue.
Keywords: problem, trigger, fix, automate, power