Merging sandbox into workflow with unsaved changes sometimes causes stuck version

[lmac-1]

Describe the bug

When merging a sandbox into a workflow that has unsaved changes, we are sometimes seeing a bug where the version number gets stuck. There is a workaround. Users can save the unsaved changes that are still hanging and then re-apply their changes.

Update: this same issue has been reported when a user deploys via OpenFn CLI.

Version number The version of Lightning you have seen the bug on.

If you're running on a tagged version, include the number: v2.15.16

I have reproduced this locally on main:

• Yes
• No

To Reproduce Steps to reproduce the behavior:

It's not easy to reproduce. Doesn't happen in every scenario but it is somewhere around this:

1. User creates a new workflow
2. User creates a sandbox of the workflow
3. User adds a new job in the original workflow and doesn't save. Keep the tab open. Call this tab A.
4. In a new tab (tab B), user goes to sandbox and adds a new job in the sandbox. Saves.
5. Merge the sandbox into main in tab B.
6. In tab B, open the workflow.
7. Observe that it loads with v1 rather than latest but the URL has no v= parameter
8. Tab A still shows "latest"
9. In Tab A, if you click on v1, it will show you actually what v1 is (the workflow before we added any job)
10. In Tab A, if they click latest, it updates to v1 and shows the workflow of v1 with unsaved changes on top.
11. You can't get back to latest unless you click "latest" and click Save.

Expected behavior Version shouldn't get stuck.

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Add any other context about the problem here.