Needs Attention
Needs Attention is reserved for run states that genuinely require you to act — not for every automatic retry or recovery step.
AgentDock Pro
Needs Attention is part of AIgency, available only in AgentDock Pro.
AIgency recovers from a lot on its own — capacity waits, workspace contention, bounded retries — without ever surfacing them as something you need to look at. Needs Attention exists specifically to avoid burying the states that actually do need you in a stream of routine automatic recovery noise.
What lands here
- A task in
waiting_interaction— an agent raised a genuine mid-turn question, permission prompt, or unrecognized state that AIgency can't resolve on its own. See Interactions and questions. - A task or run that's
failedafter exhausting its retry and fallback budget. - A run waiting on the final human sign-off step at completion. See Approvals.
What doesn't
waiting_capacity and waiting_workspace are deliberately excluded — both are scheduler/provider conditions that resolve automatically (a capacity recheck, the next scheduling pass) and never count against a task's retry budget. Surfacing these as "needs attention" would train you to ignore the signal. See Capacity recovery.
Related
- Execution — the full task-status lifecycle.
- AIgency troubleshooting