Command Center

Command Center is your workspace-wide run inbox. Open it from the Console sidebar at Command Center (/command-center). Use it when you need to approve human tasks, pause or stop runs, or triage recent failures — without opening every workflow in Workflow Studio.

​

What you see

Command Center organizes runs into four sections: The page header shows badges when action is needed:

• N pending — human tasks waiting for approval
• N draining — graceful stops still winding down

Data refreshes automatically every 3 seconds when there are pending approvals or active runs, otherwise every 30 seconds.

​

Awaiting approval

When a workflow hits a human_task step, the run pauses and tasks appear here grouped by workflow and run. For each pending task you see:

• Workflow name and run ID (first 8 characters)
• Task type (for example, approval)
• Step ID that triggered the pause

​

Approve or reject

​

Running now

Active runs appear with status badges:

​

Run controls

From Running now (and Stopping gracefully), you can: Click Open run to jump to Workflow Studio’s event log for that run.

​

Stopping gracefully

When you choose graceful stop, the run moves to Stopping gracefully until all in-flight steps complete. The badge reads Draining. If a drain takes too long, escalate to immediate stop from the same row. A drain timeout surfaces as DRAIN_TIMEOUT in the failure log.

​

Failed recently

Runs that failed or were stopped in the last 24 hours appear here. Open the run in Workflow Studio to read step-level error messages and failure_code values. Common failure codes: See Troubleshooting for recovery steps.

​

When a run looks stuck

Work through this checklist:

1. Check status in Command Center — Is it paused, draining, or waiting on approval? Complete the human task or resume if paused.
2. Open the run in Studio — Read the event log for the last step started. A step stuck in running may be waiting on a slow MCP call or LLM response.
3. Try pause then stop — Pause prevents new steps. If still stuck, use immediate stop.
4. Check connections — MCP binding failures often show as MCP_TOOL_FAILED on the first tool step. See Troubleshooting.
5. Check credits — INSUFFICIENT_CREDITS blocks new runs and can fail in-flight billing gates.

Runs waiting on human approval are not stuck — they are designed to pause until you approve or reject.

​

API equivalents

​

Related docs

• Runs and observability — run lifecycle, failure badges
• Run recovery (roadmap) — planned continue-from-failure
• Human tasks — authoring approval gates
• Workflow patterns — approve-then-send and error handling