Debugging flows, exclude steps temporarily

Have you ever tried debugging flows? Did you want to exclude some steps in your flow temporarily? Just so that you can test the steps that are failing.

Especially on long running flows, it can be a painful process if you have to run your whole flow. Running a whole flow just so that you can test if the last step works as expected can waste a lot of time.

This is a bit like a road where you want to open a bridge but you don’t want to remove the bridge forever.

My Process

Today my flow runs a Long process and a compose action that I need to debug.

So in this case I want to disable the Long Process, however I still want to run the Failing step that needs debugging.

Run after actions

In the past I added a condition that was always false. An alternative is to use the run after actions. as shown below not selecting any run after actions will result in Every run must have at least one status checked. That is a bit of a shame.

But there is hope.

Simply tick the is skipped or has timed out and

But now your step that needs debugging will not run. We just do the same trick again:

Now the long process will be skipped and the step that we want to run will run. When you’re done with the debugging simply undo the two run after configurations and it a job done!

Pieter Veenstra

Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like. I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide. For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions. SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/ Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/ You can contact me using contact@sharepains.com

Pieter Veenstra

Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like. I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide. For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions. SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/ Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/ You can contact me using contact@sharepains.com