Hung Run Recovery
When to use
- •Command shows no progress for an abnormal duration.
- •Session polling continues without output.
- •Orphaned child processes remain after script exit.
Protocol
- •Confirm hang signal:
- •no useful output over a defined window, and
- •no expected CPU/disk progress.
- •Locate specific process by command line (not broad kill).
- •Terminate only matching processes.
- •Re-run with safeguards:
- •timeout budget,
- •output heartbeat,
- •smaller scope where possible.
Safety rules
- •Never blanket-kill all
dotnet/pwshprocesses. - •Always match by command line intent.
- •Log what was terminated and why.
Repository reference
- •Used during post-clean smoke test recovery in
docs/05_Operations/Progress/progress.md.
Exit criteria
- •Hung process is cleared.
- •Re-run succeeds or fails fast with actionable error.