I have a simple flow to email me when an alert is triggered. It keeps showing as failed with the following errors
Could you please share some details regarding the flow you created?
I will check to see if I could reproduce the error you mentioned here.
Thanks for providing the corresponding ID.
For the Alert ID, would you please explain a bit for that?
Based on a research, it seems error code 429 is caused by too many requests.
If convenient, please also provide the flow configuration details, so that I could provide additional reproduce steps to the corresponding team.
The Alert ID is the ID for the PowerBI alert that triggers the flow.
I do see that the 429 is a too many requests error, but I only have 1 flow targetting this alert (for the whole team).
You shouldn't need flow config details, as it's a trigger that's failing so the actions that follow shouldn't matter, but it basically follows this template: https://ms.flow.microsoft.com/en-us/galleries/public/templates/25ba05f0f4f211e68399ffaad54805ff/crea...
I'm getting the same error for a very simplistic flow: When a Power BI Alert is triggered, send a mobile notification.
429 error simply mean that a connector is hitting the limits. Most likely slowing things down a bit will help.
A while back I looked at how to slow things down.
In short you will need to look at the peeks and maximum number of runs within the period of time that a connector can time out. Then adjust the trigger's timeout settings so that they do not time out.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Announcing a new way to share your feedback with the Power Automate Team.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
Join Priya Kodukula and the licensing team, super users and MVPs to find answers to your questions on Power Automate licensing.