Skip to main content
Product screenshot showing Ergo AI chat, sources, actions, and scheduled runs. History is the source of truth for whether a scheduled run queued, ran, succeeded, failed, skipped, and delivered.

Who can use this

  • Users monitoring scheduled runs.
  • Admins investigating failed or missing deliveries.

Before you start

  • Open the scheduled run you want to inspect.
  • Know the expected schedule and destination.
  • Check whether the run was scheduled or manually triggered.

Steps

  • Open Scheduled Agent Runs.
  • Select History on a run.
  • Review recent health indicators on the run card.
  • Select a specific execution in the drawer.
  • Check status, timestamps, duration, agent text, delivery result, failure stage, and error message when available.

What to expect

  • Execution statuses can include queued, running, succeeded, failed, or skipped.
  • The list refreshes while runs are queued or running.
  • Recent run health is summarized on the run card.
  • Manual Run executions and scheduled executions can both appear in history.
  • A failed run may include a failure stage and error message, but not every failure has the same detail.

Common issues

  • A run is still queued or running, so final delivery is not available yet.
  • The agent completed but a delivery destination failed.
  • The schedule has no upcoming next run because the run is disabled or incomplete.
  • History is filtered to the wrong run.
Last modified on June 8, 2026