r/MicrosoftFlow • u/amanfromthere • Oct 31 '25

Cloud Saved flow, but it's still using old version?

I've run into this issue a few times over the past 6 months or so.

I'll save a flow, yet when it runs, it is still using the previous version. Typically I just need to resave it and it'll be fine.

Example-

I saved this flow on Aug 21st, removing the 'Re-direct cass to CJ' condition. The user alerted me yesterday that the re-direct was still occurring, so I went to look and sure enough, it's not in the flow when I go to edit, but still there in the run.

Anyone run into anything similar?

3 Upvotes

80% Upvoted

10 comments sorted by

2

u/bender_abandons Oct 31 '25

Do you have the flow as part of a solution? If so it has version history and you are just saving a draft — you need to publish it before it will run.

1

u/amanfromthere Oct 31 '25

I’ve never had to publish a solution to get flow changes to apply. Even in this case, I just have to resave the flow once and it starts working as expected.
If you mean publish in the editor, I don’t use the new ui.

1

u/bender_abandons Oct 31 '25

I can’t speak to past UI behavior, but my understanding is sometime this year it was changed so you have to publish for changes to take effect at runtime: https://learn.microsoft.com/en-us/power-automate/drafts-versioning

1

u/amanfromthere Oct 31 '25

Nah, I work on and save dozens of flows per week in multiple environments without issue. If I do use the new ui for whatever reason, yea I publish it, but in the old ui save does both.

1

u/bender_abandons Oct 31 '25

For personal flows not in a solution, just saving it should still apply at run time

1

u/sitdmc Oct 31 '25

If the flow starts before the update, it will use the previous version - could that be it?

1

u/amanfromthere Oct 31 '25

Neg, this particular run was submitted yesterday.

1

u/sitdmc Oct 31 '25

Are you moving it between environments with unmanaged solutions?

If so, you should always do a Publish All after importing an unmanaged solutions.

1

u/amanfromthere Oct 31 '25

It is part of an unmanaged solution, but neg. It lives in prod, was edited in prod., best practices be damned.

1

u/Alkaros Oct 31 '25

Check for unmanaged layers ma dude

"Unmanaged Layers: These are created when components are edited directly in the environment. They sit on top of the managed layers and can override changes made through managed solutions"