So you have built a flow and there is just that one step that you want to disable for a while. It is always those steps that you want to disable that took a long time to put together.
Did you add an always false condition or did you use run after settings to disable an action?
In my flow example below I just want to disable he Create table action for a while. In this post I will show you an easy way to do this.
Just 3 clicks to disable an action in Power Automate 1
In the ellipses menu of the action you will find the Static result feature. It hasn’t been enabled for all actions, but for quite a few it has.
Just 3 clicks to disable an action in Power Automate 2
This gets you to the Enable Static Result toggle. Switch it on and …
Just 3 clicks to disable an action in Power Automate 3
… we now could configure output that we want to be generated. But I’m just going to click on Done.
Just 3 clicks to disable an action in Power Automate 4
Now the action will be marked with a yellow laboratory glass.
Just 3 clicks to disable an action in Power Automate 5
And in my flow run the glass will turn blue and the action is successful.
Just 3 clicks to disable an action in Power Automate 6
Now when I look at the action’s flow run details I can see that OK is returned and nothing else. In other words my action has been enabled and the action configuration is ignored until I disable the static result.
Just 3 clicks to disable an action in Power Automate 7
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
Why not just make a switch enable or disabled?
I agree a switch would be nice but then this is close enough to a switch to me.
Interesting alternative use for the static results feature
Thanks a lot !