How can I compare flow versions and review actual logic changes between versions?

Hello everyone,

I am trying to understand the versioning and review capabilities available for Flows.

For example, suppose a Flow is currently at Version 25, meaning it has evolved through many iterations since Version 1.

I have the following questions:

  • Is there a way to compare the current version with an older version (for example, Version 25 vs Version 12)?
  • If I determine that Version 12 was the best version, is there a way to restore, revert, or branch from that version?
  • During the Pending Approval process, reviewers can see comments and release notes, but how can they review the actual business logic changes?
  • Is there a way to view differences such as:
    • Prompt updates
    • Added/removed Flow steps
    • Changes in AI agents
    • Changes in connectors or actions
    • Configuration updates
  • Are there any recommended best practices for maintaining a detailed change history when multiple authors are contributing to a Flow?

From my current experience, it appears difficult for reviewers to understand exactly what changed between versions. I would appreciate any guidance on version comparison, rollback, and change review capabilities.

Thanks in advance.

Hi @vivek_kumar13,

On comparing versions and rolling back, the documented versioning model for Flows is built around version types rather than a long numbered history. A flow can have up to three versions at a time, Draft (your editable working copy), Pending Approval (if your organization uses approval review), and Published (what others run). The published version is read-only, and to change it you create a new draft. Given that model, I couldn’t find any documented capability to compare two versions side by side, view a diff of what changed, or restore and branch from an arbitrary earlier version the way you’d describe reverting to Version 12. If your experience shows a higher version number, that reflects successive publishes rather than a set of restorable snapshots that the documentation describes.

On reviewers seeing the actual logic changes, during approval review, reviewers can open and view the submitted flow and its steps, approve or reject it, and leave feedback when rejecting. What I can’t find documented is any change-highlighting or diff view that shows a reviewer exactly what changed since the previous version, such as prompt edits, added or removed steps, or connector and action changes. So today a reviewer can inspect the full submitted flow, but there isn’t a documented feature that isolates the differences for them.

On change history across multiple authors, the one documented practice here is to record what changed in the publication description each time you publish, which keeps a readable history of updates. It’s also worth knowing that a flow has only one draft at a time, so when several people contribute, edits happen on that single shared draft rather than in parallel branches. Agreeing on who edits when, and writing a clear publish description each time, is the most reliable way to keep the history understandable.

Here’s the documentation I was looking at. I’d recommend giving this a read in case you have more specific questions:

Hope this helps and feel free to reply with updates or clarifications.

Hi @vivek_kumar13,

Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime.

If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.

Thank you.

Hi @vivek_kumar13,

Since I haven’t received any further updates from you, I’ll treat this inquiry as complete at this time. Please feel free to create a new post if you have more questions.

Thank you.