Failure to Inbox Starter
Adapt the success and failure branches and find a failed run in Inbox triage.
The failure_inbox template splits after collect-brief-source. Use its status and error mappings as a starting point. The draft still labels the failure delivery target inbox. The current Delivery executor saves project artifacts and rejects that legacy target. Use Inbox with workflow failure triage to track failed runs. Eligible high-priority workflow failures can produce Inbox items when the automation rule is enabled.
| Value | How the draft uses it |
|---|---|
topic | Required text passed to the collection node, initially document.read. |
$.nodes.node_collect.status | success routes to deliver-brief. failed routes to send-failure-to-inbox. |
$.nodes.node_collect.error | Mapped to the Inbox delivery node as failure. |
{
"topic": "Collect the three test sources for the operations digest"
}- Bind the source to test data. On the success branch, create a summary artifact and map its ID to project delivery.
- Replace the legacy Inbox delivery node. For a failure tracked by Inbox triage, leave a test collection failure visible in the run. Inspect the failed node and check whether triage surfaced it. Include the run link and error when creating a handoff by hand.
- If you add actions before or after collection, map any extra failure paths explicitly. Before retrying a run that may already have changed an external system, check its receipt or state.
For a run that fails before reaching the collection node, start with workflow errors and Runs and approvals.