[{"data":1,"prerenderedAt":51},["ShallowReactive",2],{"$f26pzhnzbnvre":3},{"href":4,"title":5,"description":6,"kind":7,"mark":7,"planned":8,"contributors":9,"provenance":7,"express":8,"bridge":8,"html":10,"headings":11},"\u002Fdocs\u002Fwork\u002Fhandoffs","Handoffs","How one task hands its result to the next: by outcome, by condition, after a delay, and back to you when a decision is needed.",null,false,[],"\u003Ch2 id=\"what-a-handoff-is\">What a handoff is\u003C\u002Fh2>\n\u003Cp>A task can name the tasks that run after it: its \u003Cstrong>successors\u003C\u002Fstrong>. When a run ends, the OS starts every successor whose\nrule matches how it ended. The successor's run joins the same \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fexecutions\">execution\u003C\u002Fa>, so one piece of work\ncan move from task to task, member to member and team to team, and still read as one thing.\u003C\u002Fp>\n\u003Cp>Successors are part of the task's definition, so changing them publishes a new \u003Ca href=\"\u002Fdocs\u002Fwork\u002Ftasks#versions\">version\u003C\u002Fa>.\nA successor can be any task in your enterprise. Its run is done by a holder of that task's role, on whatever team\nthey sit.\u003C\u002Fp>\n\u003Cp>A handoff happens when a run has ended. The run that hands off does not wait for its successor, and does not\nresume afterwards.\u003C\u002Fp>\n\u003Cp>Each successor is one rule:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Field\u003C\u002Fth>\n\u003Cth>What it says\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>slug\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The task to start.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>on\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The ending it follows. \u003Ccode>succeeded\u003C\u002Fcode> if you leave it out.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>when\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>A condition on the input the successor would receive. Optional.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>delayMinutes\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Wait this long before starting it: 1 to 1440 minutes. Optional.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>maxRunsPerIssue\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The loop cap for this rule. Optional; see \u003Ca href=\"#loops-and-the-loop-cap\">Loops\u003C\u002Fa>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>resumeConversation\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>For a rule that follows your decision back to the same task: carry on the conversation that asked you. See \u003Ca href=\"#your-answers-resume-the-work\">Your answers resume the work\u003C\u002Fa>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"by-outcome-on\">By outcome: \u003Ccode>on\u003C\u002Fcode>\u003C\u002Fh2>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>\u003Ccode>on\u003C\u002Fcode>\u003C\u002Fth>\n\u003Cth>Fires when\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>succeeded\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The run succeeded and named no outcome, or named plain success.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>failed\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The run failed.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>terminal\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The run ended, however it ended.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>A named outcome\u003C\u002Ftd>\n\u003Ctd>The run succeeded and named that outcome, such as \u003Ccode>needs_changes\u003C\u002Fcode> or \u003Ccode>complete\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>ceo_approved\u003C\u002Fcode>, \u003Ccode>ceo_rejected\u003C\u002Fcode>, \u003Ccode>ceo_changes_requested\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>You decided on the run's question or gate. Only your decision sets these.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Ch3 id=\"named-outcomes\">Named outcomes\u003C\u002Fh3>\n\u003Cp>A task's skill can end its run on a word that says which way the work went. The model ends its final message with\na JSON object:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-json\">{ &quot;outcome&quot;: &quot;needs_changes&quot; }\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The OS compares that word with each rule's \u003Ccode>on\u003C\u002Fcode>. A named outcome is a branch: it \u003Cstrong>replaces\u003C\u002Fstrong> \u003Ccode>succeeded\u003C\u002Fcode>, it does\nnot add to it. A run that ends \u003Ccode>needs_changes\u003C\u002Fcode> starts the rules on \u003Ccode>needs_changes\u003C\u002Fcode> and on \u003Ccode>terminal\u003C\u002Fcode>, and not the\nrules on \u003Ccode>succeeded\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Words that only mean &quot;finished&quot; (\u003Ccode>success\u003C\u002Fcode>, \u003Ccode>successful\u003C\u002Fcode>, \u003Ccode>okay\u003C\u002Fcode>, \u003Ccode>done\u003C\u002Fcode>, \u003Ccode>finished\u003C\u002Fcode>) count as plain success,\nunless the task has a rule on that exact word.\u003C\u002Fli>\n\u003Cli>A run that failed follows \u003Ccode>failed\u003C\u002Fcode> and \u003Ccode>terminal\u003C\u002Fcode>, whatever outcome it named.\u003C\u002Fli>\n\u003Cli>An outcome is only ever the model's word. \u003Ccode>ceo_approved\u003C\u002Fcode>, \u003Ccode>ceo_rejected\u003C\u002Fcode> and \u003Ccode>ceo_changes_requested\u003C\u002Fcode> come from\nyour decision; a run whose model types one fails instead.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The task's instructions to the model list the outcomes its rules route, so a skill ends on a word that goes\nsomewhere. You can define your own outcome names in these rules; the OS does not require them to appear in a\nbuilt-in list. The skill must return the exact name its rule routes. A successor that names a missing task\nstill produces a warning (\u003Ccode>successor_unknown_slug\u003C\u002Fcode>).\u003C\u002Fp>\n\u003Ch2 id=\"by-condition-when\">By condition: \u003Ccode>when\u003C\u002Fcode>\u003C\u002Fh2>\n\u003Cp>A condition is checked on the input the successor would receive:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>\u003Ccode>when\u003C\u002Fcode>\u003C\u002Fth>\n\u003Cth>True when\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>has_issue\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The input carries an issue number (\u003Ccode>issue\u003C\u002Fcode>).\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>has_pr\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The input carries a pull request number (\u003Ccode>number\u003C\u002Fcode>).\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>no_pr\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>It does not.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>has_work_item\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>The input carries a work item (\u003Ccode>workItem\u003C\u002Fcode>): one the run claimed from one of its teams' work lists, or was handed.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>no_work_item\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>It does not.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>Any other \u003Ccode>when\u003C\u002Fcode> is refused when you save the task.\u003C\u002Fp>\n\u003Ch2 id=\"what-a-successor-receives\">What a successor receives\u003C\u002Fh2>\n\u003Cp>A finished run builds one input, and every successor it starts receives the same one:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>The run's own input\u003C\u002Fstrong>, carried forward. What the OS uses to control a run (retry and resume markers) is\nleft out.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>From the run's result:\u003C\u002Fstrong> \u003Ccode>issue\u003C\u002Fcode>, \u003Ccode>repo\u003C\u002Fcode> and the pull request \u003Ccode>number\u003C\u002Fcode>, if its final JSON names them. A run that\nopens or finds a pull request names its \u003Ccode>number\u003C\u002Fcode> there: that is the only way its successors learn it, and a run\nwhose result names none hands no \u003Ccode>number\u003C\u002Fcode> on (so \u003Ccode>no_pr\u003C\u002Fcode> holds, unless its own input already carried one). A\nresult that names a pull request but no issue only fills in \u003Ccode>repo\u003C\u002Fcode> when the input has none; it never moves the work\nto another repository. If the result names a different issue or repository, the branch the work was on is not\ncarried forward.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The work item the run holds\u003C\u002Fstrong>, as \u003Ccode>workItem\u003C\u002Fcode>: an item it claimed from one of its teams' work lists with\n\u003Ccode>os.claim_work_item\u003C\u002Fcode>, or was handed itself. The successor holds the item from the moment it starts, so the runs on\none item are one execution, and a person sees who holds it on the item's history. An item is taken over only from\nthe run before it, which has ended, or from nobody. If another run is still working it, including one waiting for\nyour decision at a gate, the successor waits as \u003Ccode>pending\u003C\u002Fcode> until that run ends, then takes the item. It does not\nstart, and it does not open a gate, while the item is held. An item still waiting for a person to approve it is\nnot taken; that run starts and records why (\u003Ccode>run.work_item_not_held\u003C\u002Fcode>). An item a stopped pipeline holds is taken\nover by the retry or the successor that carries it on, and by nothing else.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Your decision\u003C\u002Fstrong>, if the run was decided by you: your note as \u003Ccode>ceoNote\u003C\u002Fcode>, and your answers as \u003Ccode>ceoAnswers\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Nothing else in the result is passed on. Your note and answers reach the \u003Cstrong>next\u003C\u002Fstrong> task only: a task that needs them\nlater has to write them somewhere lasting, such as a comment on the issue.\u003C\u002Fp>\n\u003Ch2 id=\"delayed-successors\">Delayed successors\u003C\u002Fh2>\n\u003Cp>A rule with \u003Ccode>delayMinutes\u003C\u002Fcode> starts its successor later: it waits as \u003Ccode>pending\u003C\u002Fcode> and starts once the delay has passed.\nUse it for a check that should look again in a while, such as re-reading a build that is still running.\u003C\u002Fp>\n\u003Ch2 id=\"when-the-successor-is-busy\">When the successor is busy\u003C\u002Fh2>\n\u003Cp>A task has one run under way at a time, and so does a member. If the successor task already has a run under way,\nor every member holding its role is busy with other work, the successor waits as \u003Ccode>pending\u003C\u002Fcode> and starts when the task\nand one of them are free. A run waiting for your decision at a gate does not count as busy for that task or that\nmember, so a different issue can use them. The same issue or pull request waits: a second run of that task stays\n\u003Ccode>pending\u003C\u002Fcode> until the gate is decided, and does not open another gate for it. The work item still keeps one piece of\nwork to one run at a time, gate included. The same successor is not queued twice for the same input.\u003C\u002Fp>\n\u003Ch2 id=\"loops-and-the-loop-cap\">Loops and the loop cap\u003C\u002Fh2>\n\u003Cp>A rule may point back to an earlier task: review, fix, review again. A loop made only of \u003Ccode>terminal\u003C\u002Fcode> rules would\nnever stop, so it is refused when you save it (\u003Ccode>unconditional_loop\u003C\u002Fcode>).\u003C\u002Fp>\n\u003Cp>Every other loop is capped, for work about one issue, pull request or work item (an \u003Ccode>issue\u003C\u002Fcode>, \u003Ccode>number\u003C\u002Fcode> or \u003Ccode>workItem\u003C\u002Fcode>\nin its input): each rule may start its successor \u003Cstrong>4 times\u003C\u002Fstrong> by default for that piece of work, and \u003Ccode>maxRunsPerIssue\u003C\u002Fcode>\nchanges the cap for one rule. The count starts again after each decision of yours and each time a person retries a\nrun of that work, and rules on \u003Ccode>ceo_approved\u003C\u002Fcode> or \u003Ccode>ceo_changes_requested\u003C\u002Fcode> are never capped. Work with none of these in\nits input is not capped, so give a loop over anything else its own way to stop. An issue or pull request names the\nwork when the input carries one; a work item carried beside it rides along, and names the work only when there is\nneither.\u003C\u002Fp>\n\u003Cp>At the cap, the OS does not start another lap. It records a \u003Cstrong>blocked\u003C\u002Fstrong> run with the reason \u003Ccode>loop_cap\u003C\u002Fcode>, which\nappears on \u003Cstrong>Blockers\u003C\u002Fstrong> for a person to retry or cancel. A retry by a person starts every rule's count\nfor that issue or pull request again, so the work goes on until a rule reaches its cap once more. A retry by a task\ndoes not. See \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fruns#blocked-runs\">Runs\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"when-a-pipeline-stops\">When a pipeline stops\u003C\u002Fh2>\n\u003Cp>A run that ends on an outcome no rule routes is a dead end. The run itself still reads \u003Ccode>succeeded\u003C\u002Fcode>, but the OS\nrecords that the pipeline stopped there, and which successors it did not start, and \u003Cstrong>Blockers\u003C\u002Fstrong> lists the work as\nstopped so it is not lost.\u003C\u002Fp>\n\u003Cp>A run that names no outcome at all is a dead end only when the task has neither a \u003Ccode>succeeded\u003C\u002Fcode> nor a \u003Ccode>failed\u003C\u002Fcode> rule to\nfall back on. Before it ends like that, the model is asked once to name its outcome. A task whose only rules are on\n\u003Ccode>terminal\u003C\u002Fcode> declares no outcomes, and a run of it is simply the end of the pipeline.\u003C\u002Fp>\n\u003Cp>Rules that name a task your enterprise does not have are saved with a warning (\u003Ccode>successor_unknown_slug\u003C\u002Fcode>): the\npipeline ends there.\u003C\u002Fp>\n\u003Ch2 id=\"finished-work\">Finished work\u003C\u002Fh2>\n\u003Cp>A pipeline that ends cleanly has stopped, but the OS does not know whether the work is done or only set down. A run\nthat merges a pull request and a run that parks an issue for later both end \u003Ccode>succeeded\u003C\u002Fcode> with nothing after them.\nSo a task says which of its endings finish the work: \u003Cstrong>Finishes the work on\u003C\u002Fstrong> on its page, \u003Ccode>finishesOn\u003C\u002Fcode> in the API.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>The last run ends\u003C\u002Fth>\n\u003Cth>What happens to the work\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>On an outcome its task declares as finishing, with no step after it\u003C\u002Ftd>\n\u003Ctd>It is finished. It shows as complete on \u003Cstrong>Executions\u003C\u002Fstrong> and is never listed on \u003Cstrong>Waiting\u003C\u002Fstrong>.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Any other way, with nothing after it\u003C\u002Ftd>\n\u003Ctd>It is still open. It is listed on \u003Cstrong>Waiting\u003C\u002Fstrong> until someone restarts it or marks it finished.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>List an outcome word for each ending that is the end of the work, and \u003Ccode>succeeded\u003C\u002Fcode> for a plain success:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-json\">{ &quot;finishesOn&quot;: [&quot;succeeded&quot;] }\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>A task that can end either way declares only the ending that finishes, and its skill tells the model to name it. A\ntask that closes an issue or leaves it parked might end \u003Ccode>{&quot;outcome&quot;:&quot;closed&quot;}\u003C\u002Fcode> when it closed it and\n\u003Ccode>{&quot;reason&quot;:&quot;…&quot;,&quot;waitsOn&quot;:&quot;…&quot;}\u003C\u002Fcode> when it did not, and declare \u003Ccode>[&quot;closed&quot;]\u003C\u002Fcode>. The parked issue stays on \u003Cstrong>Waiting\u003C\u002Fstrong>,\nwith the \u003Ccode>reason\u003C\u002Fcode> and \u003Ccode>waitsOn\u003C\u002Fcode> its run gave shown beside it.\u003C\u002Fp>\n\u003Cp>Three things to know:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A finish is recorded only when nothing follows the run. If a successor starts on that outcome, the work carries on.\u003C\u002Fli>\n\u003Cli>A finishing outcome is never a dead end (\u003Ca href=\"#when-a-pipeline-stops\">above\u003C\u002Fa>), even on a task whose successors branch on\nother named outcomes and none routes it: the run is recorded as finished. \u003Ccode>succeeded\u003C\u002Fcode> is never a dead end either.\nAn outcome the skill ends on that is neither routed nor finishing is saved with a warning (\u003Ccode>outcome_not_routed\u003C\u002Fcode>).\u003C\u002Fli>\n\u003Cli>New work on the same issue, pull request or work item opens it again. If that work also ends without finishing, it\nis listed on \u003Cstrong>Waiting\u003C\u002Fstrong> again.\u003C\u002Fli>\n\u003Cli>A work item the finishing run holds is closed as done with the finish, with the run named on the item's history. A\nrun that closed the item itself leaves it as it closed it. On \u003Cstrong>Waiting\u003C\u002Fstrong>, work keyed on an item is listed by the\nitem's title.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The OS does not read your issue tracker to decide this. Work you close by hand in the tracker stays on \u003Cstrong>Waiting\u003C\u002Fstrong>\nuntil someone marks it finished there.\u003C\u002Fp>\n\u003Ch2 id=\"your-answers-resume-the-work\">Your answers resume the work\u003C\u002Fh2>\n\u003Cp>A task that needs a decision from you asks it and stops. It puts one or more questions to you, each with a\nrecommended answer, and waits at a \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fgates#questions-for-you\">gate\u003C\u002Fa>. When you decide:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Your decision\u003C\u002Fth>\n\u003Cth>The run's outcome\u003C\u002Fth>\n\u003Cth>What its successors receive\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Send answers\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>ceo_approved\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>ceoAnswers\u003C\u002Fcode>, one per question, and your note as \u003Ccode>ceoNote\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Reject\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>ceo_rejected\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Your note as \u003Ccode>ceoNote\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Request changes on a gate\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>ceo_changes_requested\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Your note as \u003Ccode>ceoNote\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>Route those outcomes like any other: an approved plan on to the task that carries it out, a request for changes back\nto the task that proposed it. Rejecting a gated tool call is different: it cancels the run, and nothing follows. See\n\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fgates#what-happens-at-a-gate\">Gates\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>A rule back to the \u003Cstrong>same\u003C\u002Fstrong> task can set \u003Ccode>resumeConversation: true\u003C\u002Fcode>. The successor then carries on the conversation\nthat asked you, instead of starting fresh: the model sees what it did before, then your decision, your note and each\nanswer, and is told how long the question waited.\u003C\u002Fp>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Ch2 id=\"waiting-on-another-team\">Waiting on another team\u003C\u002Fh2>\n\u003Cp>A run will be able to hand part of its work to another team's task and wait for it (\u003Ccode>waiting_on_run\u003C\u002Fcode>): the other\nteam's run does its part, and the first run resumes when it finishes, or fails with its reason. Today a handoff\nstarts its successor when the run has ended, and nothing waits for it.\u003C\u002Fp>\n\u003C\u002Fdiv>\n",[12,16,19,23,26,29,32,35,38,41,44,47],{"id":13,"text":14,"level":15,"planned":8},"what-a-handoff-is","What a handoff is",2,{"id":17,"text":18,"level":15,"planned":8},"by-outcome-on","By outcome: on",{"id":20,"text":21,"level":22,"planned":8},"named-outcomes","Named outcomes",3,{"id":24,"text":25,"level":15,"planned":8},"by-condition-when","By condition: when",{"id":27,"text":28,"level":15,"planned":8},"what-a-successor-receives","What a successor receives",{"id":30,"text":31,"level":15,"planned":8},"delayed-successors","Delayed successors",{"id":33,"text":34,"level":15,"planned":8},"when-the-successor-is-busy","When the successor is busy",{"id":36,"text":37,"level":15,"planned":8},"loops-and-the-loop-cap","Loops and the loop cap",{"id":39,"text":40,"level":15,"planned":8},"when-a-pipeline-stops","When a pipeline stops",{"id":42,"text":43,"level":15,"planned":8},"finished-work","Finished work",{"id":45,"text":46,"level":15,"planned":8},"your-answers-resume-the-work","Your answers resume the work",{"id":48,"text":49,"level":15,"planned":50},"waiting-on-another-team","Waiting on another team",true,1794928143967]