Skip to main contentKomos gives you two places to review activity: the Execution hub for every run across your org,
and the Past runs tab inside each task. Both are designed for builders and downstream consumers
who need a quick, non-technical view of what happened.
Where to look
- Execution hub: Mission control for all runs. Filter by status, task, trigger type, time window,
or runner (sandbox vs self-hosted). Open any row to inspect the full timeline, inputs, outputs, and
logs.
- Past runs (per task): Inside a task’s detail page, the Past runs tab shows the latest executions
for that specific automation with the same columns (status, trigger, duration, runner, requested by).
Use it when you’re iterating on one task and want fast access to its recent history.
What you can see in a run
- Timeline with nesting: Parent runs list every node. Child Task nodes include a “child run” link
to open the nested execution without losing your place.
- Live status: In-flight runs stream node status, screenshots, and logs so you can spot where the
flow is waiting or failing.
- Inputs & outputs: Structured variables (including object/object_list shapes) are shown with
their current values. Download them or fetch the same data via the Task Runs API.
- Media: Download the recorded sandbox session for exact replay when you need visual evidence.
Actions you can take
- Cancel a run that’s stuck or no longer needed.
- Retry after fixing inputs or credentials.
- Export outputs for sharing with downstream teams.
Tips for clarity
- Name nodes with verbs so the timeline reads like a story (e.g., “Search invoices,” “Email report”).
- Declare task outputs and map them to variables so consumers see structured results instead of raw
logs.
- Add visual references to AI-driven nodes when page state matters; they travel into runs and help the
agent stay on target.
