Skip to content

Commit ed128ea

Browse files
only21milclaude
andcommitted
docs(server): task_cancel keeps a failed result failed
The task_cancel section said a cancelled background-only task always settles as interrupted. Only a completed result maps to interrupted; a failed result stays failed. Say so. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent b63b483 commit ed128ea

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎docs/orchestration-v2/orchestrator-mcp-server.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -305,8 +305,8 @@ Stops the child thread with the internal `thread.stop` command, then stops every
305305
task the child delegated, and disposes automatic parent delivery. Like a user Stop,
306306
`thread.stop` interrupts the running turn, holds queued turns, and ends pull request
307307
watches. A nonterminal task with no interruptible run is rejected unless its finished
308-
turn still waits on background work or delegated tasks; a cancelled task then settles
309-
as `interrupted` once its turn ends. A terminal task
308+
turn still waits on background work or delegated tasks. Once a cancelled task's turn ends,
309+
a completed result settles as `interrupted` and a failed one stays `failed`. A terminal task
310310
returns its existing status, and its child thread still stops, including later
311311
runs and watch wakes. Published task results remain available. It accepts an
312312
optional cancellation reason.

0 commit comments

Comments
 (0)