During the debug run, the save pop-up shown below keeps appearing. If the user chooses Save, it terminates the run. If they choose Don’t Save, all changes are lost. The pop-up also does not close properly and keeps reappearing, which is very disruptive.
It seems like this behavior needs improvement. Does anyone know how to control or disable this pop-up? How do you usually handle it? For complex debug automation, this pop-up becomes a major issue, leaving the developer with no option other than saving and terminating the run.
It indeed sometimes happens when running the code when it seems you havent changed anything, but thats easy to ignore, just press No and the execution continues.
If you do want to save them, you have to stop the code and need to press yes and restart.
At the end up can get this popup.
Whilst I agree it gives too many false positives, the choice you give between save and don’t save seem fair no?
The issue is that pressing the No does not help much. It runs few steps and again starts popping it however I have not changed anything in the code. Not sure but this looks like some sort of bug?
Yeah, I can see that being annoying, I think it can sometimes be changing what is effectively metadata in the workflow, such as an annotation size or if something is collapsed. Integration service activities can also ‘refresh’ and cause it to be considered changed. It could be nice if these were ignored but that might be hard.
Are you running a large single workflow? Or with execution trail on?
If the workflows are split into smaller ones, and execution trail is off, meaning it doesn’t need to open each workflow, the issue can be mitigated.
I hope this behavior is a known UiPath Studio bug Please try this steps :Save All
Close the XAML tab and Reopen it then Start debug In this way Pop-up disappears in most cases next Disable Autosave during debugging
Settings → General → Auto Save → OFF
Clear project cache give a try
I believe it can still occur. For example, if you have an integration service connection further down in the workflow that you haven’t looked at during your current session, when you scroll down to it the activity card will load and refresh the integration service connection, this can cause the workflow to be considered as ‘changed’ and then give the popup.
Same if its doing the execution trail etc, its not that the workflows are not saved before starting, as they are all saved as you start debugging, its that they change after the Save All.
Makes sense, thank you for explaining it so clearly.
The lazy loading of Integration Service activities and the rehydration of metadata during debugging seem to be triggering Studio to treat the workflow as changed again. This aligns exactly with the repeated popup issue I’m facing.
Hopefully Studio can improve this behavior in a future update.
