Monitor task runs

Follow your scheduled and webhook-triggered task runs as they happen. Open a task to see exactly what the agent did, monitor runs in progress, and act on runs that are waiting at a gate.

Before you start

Make sure you have at least one task set up with a schedule or a webhook trigger. For webhook setup, see Webhooks (Developer Setup).

Find and open a run

Each time a scheduled or webhook-triggered task fires, it creates a run. Runs live on the task itself: the task detail view shows each run, and the activity panel below the task description logs each run's events, so you can see what the agent did and whether anything needs attention.

Scheduled tasks appear under Scheduled in your Tasks list. Each one shows when it last ran and when it runs next.

Understand a run waiting at a gate

When a task run reaches a gate, it waits there before continuing. In the run's thread, the status shows Awaiting Approval. On task lists, the run-health badge shows Awaiting gate. This is not the same as a paused schedule: Paused on a task means its schedule is paused. A run waiting at a gate is mid-run, not stopped.

Gate behavior differs by type:

• Approval gates wait until someone acts on them. The approval card appears in the run's thread. Open the run to find the card and respond.
• Timeout gates clear automatically when the wait time elapses. The default wait is 24 hours.

If a run has been waiting at a gate longer than expected, open the task to see which gate is waiting and what action is needed.

Troubleshooting

A scheduled run did not fire. Check whether the task's schedule is paused. If the schedule is active but the task still did not run, check the timezone saved in the schedule. It runs at the scheduled time in the saved timezone, not your current location.

A run shows Awaiting gate for a long time. Open the task to see the gate type. Approval gates show Awaiting Approval in the run's thread and require someone to act on the card there. Timeout gates clear on their own. The default wait is 24 hours.

A webhook task is not running. Check whether the webhook subscription is active. A paused subscription ignores incoming events. See Webhooks (Developer Setup) for subscription management.