Flow triggering an older version?

[Elena Pomana]

Hello,

I have a flow that has several versions. The newest one is the one that we need (it is saved + published) but when we trigger it, somehow in executions we see that an older version is triggered.

How is this even possible?

I have checked the flows versions in sys_update_version and I see that the "currect" and last entry is the latest/correct version of the flow.

Any ideas?

Thank you,

Elena

[4b0d3]

Can you look at the executions?  See if maybe a flow is very long and still running in the previous version?   also,  how much did the trigger change from the old to the new?  I've experienced some issues changing the trigger of an established flow on prod, where we had to disable/delete the original and add in the new one.

[Elena Pomana]

Hello @4b0d3!

Sorry for the late response, I didn't see there was a comment to the post.

I did check the executions and this is how we noticed that it triggers the old version. The flow isn't that long, it contains 18 actions so that won't be a problem.

The trigger didn't change at all, the only "difference" is a wait for condition that was added to the newest version.

It is an order guide that triggers 12 cat items and this is part of that and it needs to create an email address for the new joiner. The problem that we encounter is that when the flow is triggered at the same time for 3 or more users and it needs to create 3+ different email addresses, it creates for only 1 or 2 users and the rest are left behind.

This is the reason why wait for condition was added.

Thank you,

Elena

[Ankur Bawiskar]

@Elena Pomana 

Did you try creating a fresh flow and publish it and attach it again?

[Elena Pomana]

Hello @Ankur Bawiskar,

Yes! Tried 2 things:
- duplicate the existing flow and use it instead of the "old" one.

- create a new flow from scratch and use it

Both ways show the "old" version. 

I don't know how this is possible, especially for the 2nd one.