Switching flows on a Pre-existing list

[Lucaso1]

Hi,

I created a simple approval Flow, but had to tweak a few things here and there; I created a "test" SHP to work out any bugs on this new improved version before going live. Both Flows trigger whenever a register is created in a list.

The problem I've come across is that, when I tried to switch Flows i.e. turning the original flow off and the new one on, the new flow started running on previously completed registers; is there anyway to make the flow trigger only in new registers after the flow is turned on?

[efialttes]

Hi!

Which trigger are you using in both cases? Sharepoint 'When a new item is created or modified'? if so, please note there is a trigger called 'When an item is created'. 

Hope his helps!

[Lucaso1]

Hi,

Thanks for answering; both run on "When an item is created" Sharepoint trigger.

[efialttes]

Hi!

So probably it's me that did not understood your challenge. What do you mean with 'the new flow started running on previously completed registers'?

Thanx!

[Lucaso1]

My bad, prolly wasn´t clear enough.

List A is running with flow A. 

After a few days, Regsiter X is created in List A; Flow A is triggered by register X, and runs succesfully.

Flow B is ready to be implemented; Flow A is turned off; Flow B is turned on and starts running on List A; previously existing X register is modified by Flow B, which Flow A has already run on.  

[efialttes]

Hi

Both Flows run over the same List A?

You mean Flow B, whose trigger is 'when an item is created', has automatically been executed on an item that was created before turning on Flow B?

Thanx!

[Lucaso1]

Exactly!

[Lucaso1]

I'll also add,

List A had around 170 registers and Flow B ran in about 48 of them; also, the order was completly random, some older registers some in newer ones and some in between; just turned it on again a it dind´t run on the rest, tried creating a new register and worked fine.

[v-alzhan-msft · Accepted solution]

Hi @Lucaso1 ,

It is the expected behavior if you turn off and turn on a flow, then flow would immediately  run for the items that should trigger the flow when the flow is turned off.

You could vote for the ideas that the flow would run the items when it is turned off:

https://powerusers.microsoft.com/t5/Power-Automate-Ideas/Turning-off-Flow-and-turning-back-on-still-...

As an alternative way, I would suggest that you could create new flow or copy a new flow from the turned off flow if you don't want the items during turned off to run.

Best regards,

Alice       

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[efialttes]

Alice

Thanx for clarifyig the expected behaviour... I din't know either this collateral effect from switching off and on. Do you know if  this happen with Sharepoint connector only, or as a general rule with any connector?

Thanx!

[v-alzhan-msft]

Hi @efialttes ,

Not only the sharepoint connector, the OneDrive connector, outlook connector also the same, it is the general rule for new or updated item that would trigger the flow.

Best regards,

Alice       

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Lucaso1]

Understood, basically any improvement on Flow A once it has been turned on, has to be "coded" straight into Flow A; switching flows is not a viable option, since it will always rerun old registers, since they are "new" to flow B. Any reason why it seems to run on a schedule? I acutally set up a delay timer so I could cancel all runs before they altered information, but the flow ran every 3 hours on different list items.