What you’ll see
Every run shows what kind of activity it was, when it happened, whether it succeeded, and how long it took. Failed runs show why they failed in plain language, so you usually don’t need to dig further to know what to fix. Use the filters above the list to narrow down what you’re looking at:- Module — Tool or KB sync.
- Status — Pending, Running, Success, Failure, or Timeout.
- Trigger — what caused the run: a call ending, the genie invoking a tool live, a manual test, a scheduled knowledge sync, a connector sync, or a retry of an earlier run.
Retrying a failed run
Click into a run to see its detail. If it’s a capability (tool) run that failed or timed out, you’ll see a Retry button — fix the underlying issue (an expired connection, for example) and click it to run that step again immediately, without waiting for its next trigger.Retry is only available for tool runs that failed partway through a step — not for knowledge syncs. If a knowledge sync fails (for example, it couldn’t reach its source), there’s no retry button on that run; go to the sync itself on the genie’s Before tab and use Run now once you’ve fixed the issue.
Per-genie activity
Each genie also has its own Activity tab, showing that genie’s stats for the period at a glance — knowledge syncs, tools used, and follow-ups fired — followed by a day-by-day timeline (Today, Yesterday, then by date) of that genie’s calls and syncs. Use Refresh to pull the latest. This tab doesn’t have a retry action; to retry a failed tool run, use the main Activity log instead.Call detail
Click into any call to see it broken down by Before, During, and After — what knowledge it drew from, what it looked up mid-call, and what happened once it ended. This is the fastest way to understand exactly what a genie did on a specific call.