We are experiencing an issue in Studio 2025.10.6 LTS during Remote Debugging.
Studio repeatedly shows the message:
This change cannot be done while debugging. Would you like to keep the changes and stop execution?
even though no changes have been made to the workflow.
Selecting No does not continue execution. Instead, the same dialog immediately appears again, resulting in an endless loop. The only way out is to select Yes and stop the debugging session.
I found older reports of similar issues, but I’m wondering if anyone has found a workaround or fix for this in recent Studio versions.
I’ve seen similar behavior during Remote Debugging when Studio detects a workflow change even though no intentional changes were made.
As a workaround, you could try the following:
Close and reopen Studio and start a fresh Remote Debugging session.
Check whether the workflow/XAML is being modified or synchronized by source control, OneDrive, or another process during debugging.
Make sure the local project and the remote project are on the same version and that there are no pending changes.
Try using Save All before starting the debugging session.
If possible, test with a copy of the project or a simple workflow to confirm whether the issue is project-specific.
Also check the Studio logs around the time the dialog appears, as they may indicate what change Studio is detecting.
Since you are using Studio 2025.10.6 LTS, it would also be worth checking whether the issue is reproducible on the latest available patch/build or whether it has already been addressed.
If the issue still occurs, sharing the Remote Debugging configuration and relevant Studio logs would help identify the cause.
This looks like a known bug that UiPath fixed in a later patch of the same LTS line.
The Studio 2025.10.8 release notes list a fix where Stop Execution windows appeared unexpectedly while debugging some projects when Studio marked files as modified when opening them. That matches your issue here. Studio - 2025.10.8
Hi @jorgen.letnes ,
Can you please match Studio/Robot versions, restart the debugging components, test a clean project copy, and escalate with logs if it persists.
Upgrading to 2025.10.17 seems to have resolved the issue on our side. A colleague who is still running 2025.10.14 continues to encounter the bug occasionally, which suggests the actual fix may have been included in a later build than indicated in the patch notes.