A way to bypass Triggers

[skatofia]

Hi,

Is there a way to disable certain triggers in a flow so that it can continue to the next trigger? For example, keep a delay trigger in the flow but bypass it on a manual test and keep the trigger as a place to turn on later?

Thanks!

[trice602]

Hi @skatofia ,

There are a lot of ways to do this but first let's review what a trigger is.  In a flow there is only one trigger, everything below the first step is an action; and guessing that is what you meant as I read the context of the question.

That said, I will give you some examples:

1) say I have a flow that has the action "list rows present in a table".  In testing, I may have a column that has my email address in it so in my flow, I have a conditional action that checks that variable, and if true, adds a delay, else keep going without the delay.

2) say I have a trigger that says when a new email arrives.  In testing, I may have a conditional action that adds the delay if it is from a testing email address, else keep going without the delay.

3) say I have a flow that is processing an email body.  In testing, I may insert a special key sequence, such as, "AAA12345" and if found in email body (through a conditional action), add a delay, else keep going without the delay.

Goes without saying, there are lots of ways to do this, even outside of the above examples, but hope this helps enough to give you some ideas.

[skatofia]

Hi @trice602,

Do you have to create condition actions to do this? Or is there a way to edit the action and select 'don't run with flow' or something?

[trice602]

Hi @skatofia ,

The option you have in the trigger are trigger conditions but those conditions will launch the flow or not launch the flow but it doesn't give you other flow options such as adding a delay.

I think conditional action works.  Here's another example:  If my email body contains the text "testing" add in my delay else keep going without a delay.

[lbendlin]

Is that for Power Automate Cloud or Power Automate Desktop?

On Desktop you can disable individual steps.  In the cloud you need to hide those steps behind a Terminate/Success step or in a Choice branch that will never be called.

[skatofia]

@lbendlin Can you example screen shot both scenarios?

[lbendlin]