Monitoring Runs
Every tool execution creates a run. The Runs page gives you one place to monitor activity, inspect what happened, and investigate failures. Admins see every run in the organization. Members see only their own runs, unless an admin turns off Members only see their own runs in Settings.
For a client, the run history is the audit trail of the migration and of every sync since go-live.
Monitor tool activity
Section titled “Monitor tool activity”The table shows the operational state of each execution:
| Column | What it tells you |
|---|---|
| Tool | Which saved tool was executed |
| Status | Whether the run is running, successful, failed, or aborted |
| Trigger | Whether it came from a manual run, the agent, API, CLI, MCP, a schedule, an incoming webhook, or a tool chain |
| User | Who initiated the execution |
| Started | When execution began |
| Runtime | How long the execution took |
Filter and search runs
Section titled “Filter and search runs”Use the status, system, trigger, and time filters to narrow the table.
Search matches run IDs, tool IDs and names, users, and errors.
Inspect results
Section titled “Inspect results”Expand a run to inspect the complete execution context in place. The details can include:
- Run ID, trigger, timestamps, and duration
- The input passed to the tool
- Every execution step with its status, output, and error details
- The final result or failure
- Produced files and download links
This makes the run record the source of truth for both successful outputs and debugging context.
Investigate a failure
Section titled “Investigate a failure”Start with the failed step and its error details. Then ask the agent or reproduce the run.
Ask the agent
Section titled “Ask the agent”Click Investigate to open the agent with the run context preloaded. The agent can explain the failure and compare the saved tool with the version used for that execution.
Reproduce the run
Section titled “Reproduce the run”Click Load Run to open the tool editor with the same input. Reproduce the behavior and test a fix.
Store and manage results
Section titled “Store and manage results”Store full results
Section titled “Store full results”Organization admins can turn on Store run results in the Run settings section of Settings. This keeps full inputs, outputs, and step results for later inspection. It is off by default.
Run records do not depend on full-result storage.
Delete run history
Section titled “Delete run history”Admins can permanently delete run history, any stored results, and run output files from Settings when required by their retention policy.
How far back does text search go?
Section titled “How far back does text search go?”Text search covers the most recent 30 days, including when the time filter is set to All time.
Can I stop a run that is still in progress?
Section titled “Can I stop a run that is still in progress?”Yes. Runs that are still in progress can be aborted directly from the table.