Azure
The "Save" workflow in VSCode doesn't always work correctly
Severity
P3 - Medium (Minor functionality affected)
Describe the Bug with repro steps
In any workflow iny action, got to the action "settings", change the Run After, click "Save". Close your workflow, re-open. You will see that you changes have not been saved.
The workaround: After making a change in the "Run Settings" go to the "Tracking" section, type in something, then remove and then "save".
What type of Logic App Is this happening in?
Standard (VSCode)
Are you experiencing a regression?
No response
Which operating system are you using?
Windows
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
Screenshots or Videos
No response
Environment
Browser: Edge Extentipon: 5.165.5
Additional context
No response
I experience this a lot too (and not just for this specific case). That I make changes in the designer, press the "Save" button. It gets marked as disabled as though everything was saved but in reality nothing was saved.
It happens enough that I just don't trust it anymore and now usually do a rename of an action (to re-enable the save button) and then press save and rename again and save again. (on the grounds that at least one of these attempts will likely succeed)
It is very annoying to lose work due to this.
@asos-martinsmith I do the same thing with every single save. Some things are more problematic like adding comments to an action, reordering actions, or changing an action's run-after setting.
I also switch to another vscode tab and back after saving which seems to make the designer re-render, which sometimes reveals the actual state of the workflow. For example, some actions will revert back to their last position after reordering.
Although, if you switch tabs before you save you risk losing work after the re-render.
