Hello @Community Alums!

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

@Elena Pomana 

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

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.

@Elena Pomana 

I would suggest to raise a HI case with ServiceNow and let them investigate on this issue.

Do share the resolution once ServiceNow shares some update.

Hi @Ankur Bawiskar,

Hope you are doing well.
Please can anyone help me with the below query, It would be helpful.

Lets say a flow is already running and few records have execution of that flow which are in progress.

my question is if we update the flow will that update the execution flow of that particular record as well or do we need to submit the record again for the latest execution.
If we need to submit the record again is there any workaround we can implement so that older execution flow is replace with new  flow.

Please can you share reference material if we have any.

Thank you very much in advance

Regards,

Prajwal