Skip to main content
Run History (/observe/run-history) is the platform activity and compliance event log. It contains audit events associated with workflows, registry changes, deployments, governance, and other platform activity. For operational workflow-run triage, use Production → Runs.

What you can do

  • Filter platform audit events by time range, category and search text, and switch between Table and Timeline. See Find evidence.
  • Save a view, copy its link, or export the loaded rows as CSV. See Save or share the view.

Find evidence

  • Choose a time range, category, and search text. The filters are retained in the URL.
  • Select a summary card to narrow the category. The cards cover total events, workflows, registry activity, deployments, failures, and cost impact.
  • Switch between Table and Timeline without changing the loaded event set.
  • Use Governance for a quick governance-category filter.
  • Expand a row or use its preview control to inspect the available event, run, agent, or resource detail. Trace and pivot links appear only when the event carries the corresponding identifier.

Save or share the view

Use the saved-views menu to save the current filter or reopen an existing Run History view. Copy View Link copies the current URL so another authorized operator can open the same filters. Access to the link does not grant access to its underlying evidence. Choose Export CSV to download the currently filtered, loaded audit-event rows. The export is not a workflow-run bundle and does not include events that have not been loaded. Choose Load more when it is available, then export again if you need the larger loaded set. An empty filtered view does not prove that no matching platform activity exists outside the loaded window or your readable scope. Clear filters, widen the time range, or investigate the owning run before drawing that conclusion.

Key state to watch

  • Failures and cost impact — the summary cards that narrow the log to those events.
  • The loaded set — export covers only loaded rows; choose Load more first when you need more.
  • An empty filtered view — it does not prove no matching activity exists outside the loaded window or your readable scope.
  • Events: the live stream the log is built from.
  • Saved views: reuse a filter.
  • Runs: open the run an event belongs to.