Triggered flow uses older version

Hey guys,

Noticed a strange behavior with a workflow set (triggered) to run every morning at 8am.

I realized it was running a much older version (like cached) version of the workflow, not reflecting the last saved version of the flow - like frozen in time. Hopefully it’s a one-time bug and disabling/reenabling the trigger will make the scheduled flow use the most recent version from now on ?

Could you please confirm that the expected behavior is that a triggered workflow will always run the most recent version of the flow ? And that we can confidently open the flow, change something, save and then the next flow execution will apply our last changes ?

Thanks and all the best,

Romain

Hey @cdromain – I believe the trigger is running on an older version/checkpoint of the flow.

If you click on the Save menu you’ll see an option to Save & Make this Checkpoint Live – this will make you current working draft the live version and any changes you make would be reflected in real-time. You only have to do this once.

1 Like

Hey @Rithen_Gumloop, thanks for your quick reply, hope you’re fine !

That must be it - here’s what happens when you sleep on a new feature :sweat_smile:

Cheers,

Romain

1 Like

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.

Hey Romain, No worries at all! Glad that sorted it out :blush:

Hope you are doing well too!

1 Like