Agents · Monitor
Once an agent is live, its Runs tab shows everything it has done — every time it fired, the steps it took, and whether each run worked. Use it to check a new agent is behaving on real triggers, and as the first place you look when something seems off.
Open your agent's run history
Open the Agents section and select the agent you want to check — say, your Waitlist Appointment Confirmation agent.
Open its Runs tab at the top of the agent builder. Every run the agent has done — whether a schedule fired it or an event in a connected app (a new booking in your scheduling tool, a form in Healthie) — is listed here, newest first.
Read the runs list
Each row is one run, showing a short summary, its status — completed, failed, or still running — when it happened, whether it was a test run, and the credits it used. The list covers the last 7 days — runs older than that are deleted automatically. A scheduled agent that runs every 15 minutes still builds up hundreds of rows in that window, so two tools help you get to the one you care about:
Finding a specific run
- Filter by status — show only failed runs when you're chasing a problem, or only completed ones to confirm the agent is healthy.
- Search — type to search across the run history and jump to the runs that match.
Inspect a single run
Click any run to open its detail. This is the step-by-step record of what the agent actually did:
- The trigger input — what fired the run and the data it received (e.g. the new patient-intake record from Healthie, with the fields the agent was handed).
- Each step the agent took — its reasoning as it worked through the task, in order.
- Every tool it called — and what came back — e.g. Get patient in Athena Health returning a match, then Create appointment returning the booking.
- The final outcome — where the run ended, e.g. the confirmation posted to your #patient-intake Slack channel.
- Every tool call returned a result, not an error. An error icon on a step means that call failed — even if the final message reads fine.
- The final outcome matches what you asked for. Compare it to the agent's instructions; if it references records that never came back from a successful tool call, treat it as unreliable.
- No tool is called over and over with near-identical inputs. That repetition is the signature of a run that's looping.
Using the AI copilot to check a run
Ask the AI copilot — the chat panel on the left of the agent builder — about any run. For example, "Why did yesterday's 8 AM run fail?" It reads the run, tells you what went wrong, and can debug the agent for you.
To read a run yourself, follow the steps below.
Debug a failing run
When a run fails or stalls, open it and read down the steps — the point where it went wrong is usually right there in the sequence. Errors at the very start, when the trigger fires, are captured too, so a run that never really got going still tells you why.
Reading a failed run
Look for the error icon on a tool-call step — that's the signal, even if the agent carried on and produced a final answer. Expand that step — it shows the error message and the reason the call failed, not just the arguments the tool was sent (for example, Athena Health returns a 400, or Slack returns "channel not found"). The fix usually lives in the agent's instructions or its authentication, not in the run itself — see Troubleshooting agents for the failure-mode-by-failure-mode checks.
Check your credit usage
There are a few ways to check:
- The Runs tab shows the credits used per run, for each agent.
- Billing shows your monthly credit allowance and a usage breakdown per agent.
For how credits are counted, see AI credits: how agent pricing works.
What gets logged — and what's protected
Every run is recorded in full — the trigger input, each step the agent took, every tool it called and what came back, and the final result. Because agents work with real patient data, healthcare-sensitive information (PHI/PII) is redacted by default in what's stored — so you get a complete record of what the agent did without exposing the underlying patient details. Run records are kept for 7 days, then deleted automatically — the runs list always shows up to your agent's last 7 days of activity.