Skip to Content
Docs are being rebuilt — start at Introduction → How it works.
AutomationTasks (Schedules)History & logs

History & logs

Every execution of a task — successful or failed — is preserved. Use history to audit, debug, and optimize.

Execution History Dialog

What history shows

  • Timestamp of each run.
  • Status (Completed / Failed).
  • Result summary.
  • Full agent output.
  • Tool calls made during the run.
  • Errors and stack traces (if failed).

Opening history

  • From the task list: View History in the per-task action menu.
  • From the task detail page: the History tab.

Using history for debugging

Failed runs are the first place to look when a task isn’t doing what you expect:

  1. Open the failed run.
  2. Read the error message at the top.
  3. Scroll the tool calls for the request that errored.
  4. Compare against a previous successful run if available.

Using history for optimization

  • Watch execution time trends. A run that took 5s for the first month but now takes 30s probably indicates KB bloat or prompt drift.
  • Watch success rate. A run that succeeded reliably and now fails intermittently usually points to an upstream change (model deprecation, integration limits, API contract change).
Execution & monitoringExternal triggers (Trello, JIRA, webhooks)