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

[Ankur Bawiskar]

@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.

[Prajwal G Vaish]

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

[Jason Yeager]

Our Tech Team saw the same. And here's how we fixed it.

1. Went to "sys_hub_flow" table; found the respective flow.

2. Change field Status to Draft.

3. Change field Active to FALSE.

4. Opened a new Flow Designer tab.

5. Activated the respective flow.

6. Validated an execution ran properly (eg to the new version).