Skip to main content
This page is being phased out. For the current way to track agent executions, see Tasks in the User Guide.
The Tasks tab shows every individual execution as a flat list. Use it to scan for failures, spot patterns across runs, and find specific executions by status or timestamp. For detailed debugging, switch to Threads to trace the full execution log.
Tasks table

Tasks table with 5 completed executions showing ID, Created At, Updated At, Status, and Internal Status columns.

​
Task table columns

​
Task statuses

​
Tasks vs. Threads

Use Tasks when you’re triaging across many runs (scanning for failures, checking completion rates). Use Threads when you need to debug a single run in depth (reading payloads, tracing tool calls). A single thread (conversation) can contain multiple tasks. Each task is one invocation of the agent or workflow, but tasks in the same thread share conversation context through session_id.
To see the full execution log for a task, switch to the Threads tab and click into the parent thread.

​
Global Tasks page

The sidebar has a dedicated Tasks page (the checklist icon) that shows tasks across all agents. Same columns, but with an additional Agent Name column so you can see which agent each task belongs to. Use the global view when you need to triage failures across your entire workspace rather than one agent at a time.

​
Triage failures

When you notice a cluster of Stopped tasks:
  1. Open the global Tasks page to see executions across all agents
  2. Scan by Status for clusters of Stopped tasks
  3. Note whether failures are concentrated on a specific date, time, or agent
  4. Click a Stopped task to get its task ID
  5. Switch to the agent’s Threads view and find the parent thread
  6. Open the execution log and look for the last successful step before the failure
Tasks for health checks: Scan the global Tasks page periodically. A healthy agent should show mostly Completed tasks. A growing ratio of Stopped tasks signals a configuration issue, a broken connector, or an upstream API problem.

​
What’s next

Threads

Trace the full execution log to find where a run went wrong.

Metrics

Spot anomalies in request volume and token usage before diving into individual threads.