fix: continue execution when initial resume wait times out - #161
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
This PR changes debug runtime behavior so that if the initial “wait for resume” times out, execution continues (instead of faulting), and adds a regression test for that scenario.
Changes:
- Update
UiPathDebugRuntime._stream_and_debugto log a warning and proceed when the initial resume wait times out. - Add an async test verifying a timeout on the initial resume wait still results in successful execution and emits completion.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| tests/test_debugger.py | Adds coverage for continuing execution when the initial resume wait times out. |
| src/uipath/runtime/debug/runtime.py | Changes timeout handling to proceed rather than yield a faulted result and exit. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
andreitava-uip
changed the title
andreitava-uip
force-pushed
the
fix/debug-resume-timeout-continue
branch
from
August 25, 2026 11:05
81e2dab to
f61331b
Compare
|
radu-mocanu
approved these changes
Aug 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A debug run starts paused, waiting up to 60s for a resume command from the debug bridge. If the client disconnects and never sends one, the run ended
FAULTED— intermittently failing resumed jobs whose debug client was no longer attached.Fix
On the initial resume-wait timeout, assume the bridge is disconnected and continue unattended instead of faulting: disconnect the bridge, then run the delegate in a single pass-through — no breakpoints, no inline resume handling. A suspension is terminal (the platform resumes it via the real trigger), avoiding unbounded waits on debug commands that can never arrive.
The explicit-quit path is unchanged.
Testing
New tests cover: timeout → continue to success with stale breakpoints ignored, suspension after timeout ends
SUSPENDED, and a failing bridge disconnect not faulting the run.Manual validation for process tools and escalation scenarios.