Skip to main content
A run is one execution of an agent. The Runs view shows what is active, what completed, and where an incomplete run needs attention.

​
Open Agent Runs

Open an agent and choose Runs to see its execution history. If the agent has no runs yet, start a test or live run first. The Agent Runs page has three parts:
  • Summary cards for Total Runs, Active Runs, Completed Runs, and Failed Runs
  • An activity chart for the selected time period
  • A table of individual runs
Agent Runs dashboard with total, active, completed, and failed run cards, an activity chart, filters, and a run table

Agent Runs combines activity totals, a trend chart, run filters, and execution history.

​
Filter the run list

Use the controls above the table to narrow the list: The run table shows the information that is available for every execution:
A schedule, webhook, API call, or manual request can start a run, but the run list groups executions by Test, Live, Action, and Build rather than by trigger source.

​
Select a Run

Select a row to open that run in the agent workspace. Decisional places the workflow in run context and opens the run summary on the right.
Completed workflow run with successful nodes and a run summary showing outputs, progress, and step counts

A selected run shows execution state on the workflow graph and a run summary on the right.

​
Read the workflow graph

The graph shows which workflow path ran and the execution state of each node. During a run:
  • A running node shows active progress.
  • A successful node is marked as completed.
  • A failed or rejected node is marked as failed.
  • A node can show several executions when it runs once for each item or row.
  • A reused result is identified when a successful test execution was reused instead of running the node again.
Select a node to review its executions. If the node ran more than once, choose the individual execution you want to inspect.

​
Read the run summary

The run summary shows:
  • Run ID, type, and start time
  • Overall progress across the workflow
  • Total, succeeded, running, and failed step counts
  • A shortcut to pending approvals when a step needs review
  • A credit warning when a step is paused for credits
  • Run output files grouped by the node that created them
Open Run Outputs to view or download an individual output file. Use Back to chat to return to the conversation without clearing the selected run.

​
Inspect a Node Execution

Select a workflow node, open Executions, and choose an execution to see what happened at that step. The execution panel can include:
Start with Error Details, then compare Input Data and Output Data. Use Live Logs or Log Files when the error message alone does not explain the failure.

​
Run Statuses

Every run has a status that tells you whether it is queued, active, waiting for something, or finished.
Pending, Running, Pending approval, Needs credits, Self-healing, and Waiting for input can still change. Completed, Partially completed, Failed, and Cancelled are final states.

​
Run and Node Actions

​
Cancel a run

Cancel is available for eligible Live and Test runs while they are active or waiting. It is not offered for Build or Action runs from the run list.
Cancelling stops remaining work. It does not reverse work that already completed, such as a message that was sent or a record that was updated.

​
Resume incomplete work

Resume is available for eligible Live and Test runs in Failed or Partially completed status. It continues incomplete work instead of starting the entire run again.

​
Retry one node

For a failed, retrying, or credit-blocked node execution, the execution panel can offer:
  • Retry to run that node execution again
  • Edit Code & Retry to adjust the node code for this job and retry it
Code entered through Edit Code & Retry applies only to that job. It does not update the agent’s main workflow or other jobs.

​
Investigate an Incomplete Run

1

Open the run

Select the Failed or Partially completed run from Agent Runs.
2

Find the affected node

Use the workflow graph and run summary to locate failed, rejected, waiting, or credit-blocked work.
3

Open the execution

Select the node, open Executions, and choose the relevant execution.
4

Compare the evidence

Read the error, input, output, logs, and approval or credit state shown for that execution.
5

Correct the cause

Fix the underlying data, credential, integration, source, instruction, or workflow configuration.
6

Continue the right scope

Retry the affected node when the execution panel offers it, or Resume the run when incomplete Live or Test work remains.

Workflows

Understand the graph and the nodes that execute during a run.

Approvals and Policy

Learn how review steps pause and continue a run.

Dashboards and Usage

Monitor activity, tool calls, and credit usage across agents.

Using Dex

Ask about agents and runs from a conversation.