Statuses

A status describes a stage the system has confirmed. Do not infer the result from an animation, model-generated text, or elapsed wait time alone.

Ordinary Agent Run

StatusMeaningWhat you can do
IdleNo Run is currently executingSend a new task
QueuedThe task was accepted and is waiting for execution capacityWait; do not send the same task again
RunningThe model or a Tool is workingObserve activity, and steer or cancel if necessary
Waiting for approvalA pending action was saved and is waiting for your decisionReview the approval card, then approve or reject
CompletedThe Run settled normallyInspect file, test, and source evidence
FailedThe Run did not finish and provides an errorNarrow the scope, repair configuration, or retry based on the error
CanceledThe Run received a cancellation request and settledInspect side effects that may already have happened

Completed means the run process finished. It does not automatically guarantee a correct business result; check the acceptance criteria.

Subagent

StatusMeaning
IdleThe node exists and has no active Turn
QueuedFollow-up work exists and is waiting to execute
ProcessingThe subagent is running
Waiting for approvalA subagent action requires the user to respond in the root conversation
CompletedThe latest Turn ended successfully; the node can still be awakened
FailedThe latest Turn failed
InterruptedThe latest task was interrupted
Outcome unknownAn external side effect may have occurred, but the terminal state cannot be confirmed
Archived / disabledThe node lifecycle is no longer active

Subagents in the right sidebar groups Queued, Processing, and Waiting for approval as active. Other latest terminal states appear as finished. A subagent conversation is a read-only observation view.

Scheduled Automation Task

A Task has two independent groups of information:

  • Enabled / Paused controls whether future scheduling continues.
  • Healthy / Needs repair indicates whether the target, model, permissions, and schedule remain valid.

Pausing does not cancel an already active Run and does not prevent Run now. When a task Needs repair, open its details, choose valid settings, and save. Merely marking its Attention item as resolved does not repair the task.

Scheduled Automation Run

StatusMeaning
QueuedThis configuration snapshot has been created and is waiting for admission
StartingThe system is binding the target and creating a root Agent Turn
RunningAn ordinary Agent Loop is executing
Waiting for approvalA background action requires a user decision
CompletedThe Run settled normally; the result may be an update, no change, or no report
FailedConfiguration, model, Tool, or execution failed
CanceledThe Run ended and did not continue

The trigger source is also shown as Scheduled, Manual, or Recovery. Recovery means the application merged schedule points missed while offline after a restart.

MCP Server

Common connection states:

  • Disabled / off: Does not provide callable tools.
  • Starting / connecting: The local process or protocol connection is not complete.
  • Discovering tools: Reading and validating the complete tool catalog.
  • Ready: The complete catalog is available for routing.
  • Waiting to reconnect: A temporary error occurred and the connection is backing off.
  • Degraded / needs attention: The catalog or connection is incomplete; inspect the details.
  • Error: Startup, protocol, or catalog validation failed.

Saving server configuration is not startup authorization. When the status shows Startup authorization required or Authorization expired, review the exact configuration again.

Why “Outcome unknown” is special

Failure normally means the system confirmed that an action did not complete successfully. An unknown outcome means the action may already have been sent. For file writes, MCP calls, browser submissions, or paid services, inspect the real state before retrying to avoid duplicate side effects.

Source verified · 2026-08-23Public site import · 2026-08-27