Monitoring Runs
Every tool execution creates a run. The Runs page gives you one place to monitor activity, inspect what happened, and investigate failures across your organization.
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 the dashboard, 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 |
Use the status, system, trigger, and time filters to narrow the table. Search matches tool IDs, user emails, input and output values, and errors. Text search covers the most recent 30 days, including when the time filter is set to All time.
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. From there you can:
- 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.
- Click Load Run to open the tool editor with the same input, reproduce the behavior, and test a fix.
Runs that are still in progress can be aborted directly from the table.
Store and manage results
Section titled “Store and manage results”Organization admins can enable Store Run Results under Settings → Runs when object storage is configured. This preserves full inputs, outputs, and step results for later inspection.
Run records do not depend on full-result storage. Admins can permanently delete run history and any stored results from Settings when required by their retention policy.