Hello folks!
Hope you all are doing well. In this article, we’ll discuss a feature that often goes unnoticed but can be a lifesaver when working with Power Automate flows—Flow Run Resubmission. We'll understand what it is, how to enable it in the Power Platform Admin Center, and when or why you might need it.
If you've ever dealt with failed or stuck flows and wished you could simply re-run a specific flow instance, this is the setting you need to know!
What is Flow Run Resubmission?
Normally, when a Power Automate flow run fails (maybe due to a timeout, API error, or data mismatch), you just see the error, debug it, and fix the logic. But what if you could resubmit the exact same flow run again without triggering the whole process from scratch?
That's what Flow Run Resubmission allows you to do—it gives you an option to resubmit a previously failed (or even successful) flow run, directly from the flow run history.
But there’s a catch. This option is disabled by default for environments due to security and governance concerns.
Why is Resubmission Needed?
Let’s take a real-world example.
Imagine you have a flow that sends a Teams message when a new item is added in SharePoint. One fine day, your Teams connector fails because of a temporary service outage. Now, your flow run fails.
Instead of going back to SharePoint and manually creating a new item to test again, wouldn't it be easier if you could just hit “Resubmit” and check whether it works now?
- Saves time
- Great for debugging
- Helps in production support
Especially for production-grade flows, where testing with live data is risky, resubmission is a safe and handy tool.
How to Enable Flow Run Resubmission?
You’ll need to be a Power Platform Admin to enable this setting.
Follow these simple steps
- Go to Power Platform Admin Center
- In the left menu, select Tenant Settings.
![Tenant Settings]()
- Click on the Tenant Settings.
- Go to the Power Automate flow run resubmission.
- Find the setting “Disabled”
- Turn the toggle ON-Enabled.
- Click Save.
![Click Save]()
Important Note. This change may take a few minutes to reflect. Once enabled, users can see the “Resubmit” option in the flow run history.
Considerations Before Enabling
While this setting is very useful, here are a few things to keep in mind.
- Security: Anyone with flow access can now resubmit runs. Make sure RBAC (Role-Based Access Control) is properly configured.
- Data Sensitivity: Resubmitting runs can re-trigger actions like sending emails, updating databases, etc. Ensure this won't cause duplicate actions.
- Testing Environment: It’s recommended to enable and test this first in a sandbox environment.
Developer Tip
If you're part of a Center of Excellence (CoE) or managing production environments, document which flows have resubmission enabled and under what conditions the team is allowed to use it.
Also, if your flow involves approvals, payments, or irreversible actions, be extra cautious. Resubmitting might re-trigger those actions, so test well and add safety checks in your logic.
Final Words
Enabling flow run resubmission is a small tweak but adds a lot of flexibility to your troubleshooting process. Especially in enterprise scenarios where time is critical, this feature can save hours of effort.
Try it out in your test environment and see how it helps streamline your flow management.
Further Reading