Chain Signals

Chain signals are the short status labels that summarize what is happening around a Chain right now. They help you answer a simple question quickly:

Is this workflow waiting, running, blocked, or waiting on me?

Use signals for situational awareness. Use the API reference when you need exact endpoint contracts.

The Main States

Signal	Meaning	Typical next action
`idle`	No active execution is currently running.	Start work manually or wait for the next trigger.
`running`	A workflow or AI-assisted action is in progress.	Monitor progress or let the run finish.
`awaiting_approval`	Automation reached a point where a human decision is required.	Review the pending action and approve or reject it.
`blocked`	Execution cannot continue without intervention.	Inspect the failed step, credentials, or upstream dependency.

A signal is not the same thing as completion history.

Concept	What it answers
Signal	What is happening right now?
Completion state	Has the required work already been done?
Streak or period data	Has the work been completed consistently over time?

A Chain can be idle and still be healthy because the required work for the current period is already complete.

Signals work best as a shared language between product surfaces, operators, and automation:

idle means the system is ready for the next manual or scheduled step.
running means work is in flight and you should avoid sending duplicate triggers unless the workflow is designed for it.
awaiting_approval means automation paused intentionally so a human can make the final decision.
blocked means something external must change before progress can continue.

Use Start a Chao Session for a task-focused walkthrough.
Use AI Run Lifecycle to understand the broader execution flow.
Use Chain Execution Policy for the public configuration contract that influences automation behavior.