That error usually means you are hitting throttling limits on the Teams connector, not an issue with your workflow logic itself.
Since you are processing alerts from systems like Prometheus, Kibana, Lambda, etc., you can end up sending bursts of messages very quickly, and Teams connectors are quite aggressive with rate limiting. Retry policy helps sometimes, but if the connector is already throttled, retries can actually make the congestion worse.
A few things that usually help:
- Reduce message frequency if possible (batch/group alerts instead of one card per event)
- Add a small Delay action before posting to Teams during heavy alert bursts
- Avoid unnecessary Compose actions if they are inside loops
- Turn on concurrency control carefully if multiple runs happen simultaneously
Also, “Post a card in chat or channel” is noticeably slower and more failure-prone than simple message posting. If rich cards are not absolutely required, testing with a plain Teams message can improve reliability.
For critical alerts, I would strongly recommend not relying only on Teams delivery. Many teams use:
- Teams for visibility
- Email/SMS/ServiceNow as the guaranteed escalation path
Because once connector throttling starts, Power Automate cannot guarantee real-time delivery.
Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item.
If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like! 🩷
