Skip to main content
TeamCopilot keeps run history so you can inspect what happened after the fact.

​
What the history view shows

The run history tab lists recent workflow runs with:
  • workflow slug
  • status
  • start time
  • duration
  • runner identity
The current implementation shows the workflow slug, status, start time, duration, and runner identity. The detail page then shows input and logs.

​
Run detail pages

Each run has a dedicated detail page where you can inspect:
  • the run summary
  • the captured output
  • the associated logs
  • the originating session when available
The run detail view is the right place to debug a failed workflow or confirm what happened during a long-running operation.

​
What the detail page includes

  • workflow slug
  • run status
  • runner identity
  • started and completed timestamps
  • duration
  • parsed input payload
  • captured logs
  • a stop button when the run is still active

​
Log sources

TeamCopilot can fetch logs either from the workflow run record or from a session/message pair, depending on how the run was created.

​
Relationship to cronjobs

If a workflow run was started by a cronjob, the run history may be the first place you notice it. Cronjob runs can point back to the workflow run, and the workflow run detail page is where you inspect the runtime output.

​
When history matters

Use run history when you need to:
  • audit what ran
  • review a failure after the fact
  • navigate from cronjob execution back to the underlying workflow run
  • compare multiple runs of the same workflow