> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.

# Execution History

> Review past runs from the employee drawer timeline and open full run detail for logs, cost, and outcomes

## Overview

**Execution history** is the record of every run (Work Cycle wake-up or manual invoke) for a Digital Employee. In Cowork you browse it from the employee **detail drawer** — not from a standalone history app.

## Open the timeline

1. Click the employee on the Mesh Canvas
2. In the drawer, find the **Timeline** (or recent runs list)
3. Each row shows status, start time, duration, and credits used when available

Runs appear newest first. Status labels include **Running**, **Success**, **Failed**, and **Awaiting approval**.

## Open run detail

Click a run in the timeline to open its full detail view:

* **Outcome** — success, failure, or still in progress
* **Wake reason** — scheduled heartbeat vs manual invoke
* **Duration and credits** — how long it ran and what it cost
* **Logs and result excerpt** — what the employee did and produced
* **Approval history** — plan or input steps when the run paused for you

Use run detail to debug failures, verify deliverables, and understand credit spend per execution.

## Filter and paginate

When many runs exist, the timeline loads in pages. You can narrow by run status (for example, show only failed runs) when the drawer offers filters.

There is no free-text search or date-range picker in the UI today — scroll the timeline or filter by status.

## Workspace-wide scan

For a cross-employee view, use **Mission Control / Day Planner** recent-activity lanes and open employees from there. Per-employee history always lives in that employee’s drawer.

<Tip>
  Export to CSV or PDF is not available in the Cowork UI. Use the Tess API if you need bulk analysis outside the product.
</Tip>

## Tips

* Review **Failed** runs regularly — repeated failures often share one root cause (connectors, instructions, or approvals)
* Compare **Wake reason** to distinguish scheduled work from manual invokes
* Watch **Credits used** on expensive runs when tuning model or Work Cycle settings

## Next steps

* [Mission Control monitoring](/en/cowork/digital-employees/monitor-dashboard/monitor-dashboard)
* [Advanced Monitoring](/en/cowork/digital-employees/monitoramento-avancado/advanced-monitoring)
* [Work Cycle](/en/cowork/digital-employees/configuracao-de-cron/cron-heartbeat)