Why this happens
- The reminder flow is usually based on a Recurrence trigger.
- If the trigger fires while Teams or Power Automate is lagging, it can enqueue hundreds or thousands of pending runs.
- Deleting, disabling, or snoozing the reminder does not cancel already queued runs.
- Teams then keeps delivering the messages every few seconds until the queue drains.
This is a platform issue, not user error.
What usually fixes it (in order)
1. Disable the flow at the environment level
Go to Power Automate portal, not Teams:
- Find the flow
- Toggle it Off
- Wait several minutes
- Refresh the page
If the flow no longer exists but messages continue, it means runs were already queued.
2. Cancel all running and queued runs
If the flow is still visible:
- Open the flow
- Go to Run history
- Cancel any Running or Waiting runs
This is the most effective fix if you can still access the flow.
3. Sign out of Teams completely
This helps only after the queue starts clearing:
- Fully sign out of Teams (not just close)
- Wait 5–10 minutes
- Sign back in
This forces Teams to resync bot delivery state.
4. Temporary workaround (what you already did)
Blocking the Power Automate Chat bot stops the flood, but you’re right that this also stops all other flow notifications. This should only be a last resort.
When nothing works
If messages are still firing hours later, the only real fix is Microsoft intervention.
Open a support ticket and reference:
- The specific flow ID (you’ll see it in the error history)
- That this is a runaway recurrence trigger in Power Automate → Teams
- Request backend queue purge
Support can clear the stuck executions server‑side. End users cannot.
How to prevent this in the future
For recurring reminders:
- Add a Terminate action at the end
- Avoid very tight recurrence schedules
- Add a control condition (for example, only send if Now is within a defined window)
- Consider using a scheduled cloud flow with safeguards, not a simple recurrence
Bottom line
- This is a Power Automate backend queue issue
- Deleting the flow does not stop already queued runs
- Cancelling runs or Microsoft support is the real solution
- You’re not the only one who’s hit this
✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.