Hi,
This is something a few people have run into, and in most cases it’s not an issue with your flow but with how version history is currently handled in flows inside Solutions.
A couple of points that may help clarify:
-
Version history only shows after a save/publish cycle
Version history is created when the flow is saved and updated. If the flow hasn’t gone through multiple save/publish cycles (especially after being added to a Solution), the panel can appear empty.
-
Solutions + new designer behavior
When working with flows inside a Solution, version history can sometimes not display correctly in the UI, particularly with the new designer. Even though versions exist, they may not always be surfaced in the panel.
-
Check if changes are actually creating versions
Try making a small change (for example, update a description or rename a step), then:
This can sometimes trigger the version to appear.
-
Environment / feature limitations
There isn’t a specific admin setting to disable version history, but behavior can vary depending on:
-
Alternative validation
Even if version history is not visible, your flow is still functioning normally (as you confirmed via run history). In some cases, this ends up being more of a UI limitation rather than a functional issue.
Based on similar scenarios, this is often related to UI inconsistency with solution-aware flows, rather than permissions or configuration.
If possible, you can also try:
If you’re able to confirm whether new versions appear after a fresh save/update, that would help narrow it down further.
Hope this helps.
If this helps resolve your issue, please consider marking the response as Verified so it can help others facing a similar scenario.
If you found this helpful, you can also click “Yes” on “Was this reply helpful?” or give it a Like.
