---
title: "History and events"
description: "What a playbook records: the definitions it saves, the runs it carries out and the events it takes in, and how triggers and pages use that history."
url: "https://on.auto/docs/concepts/history-and-dream"
last_updated: "2026-11-10T01:43:26+00:00"
---

# History and events

A playbook records what happens in it: the definitions it saves, the runs it carries out and the events it takes in from elsewhere. You read that history to see what a run did and why. Event triggers and the views of pages read it too, so what the playbook recorded can shape later work.

## What a playbook records

A playbook records:

*   each version of each definition, and when it was created, updated or retired;
*   each run: its start and input, what it did, and how it ended;
*   each tool call a run makes, and each step a workflow run takes;
*   the events published to it, and the events its workflows emit.

For example, after a campaign review you can go back to the review the run produced. You can also see the prompt it filled in, the version of "Review campaign brief" it used and the model's usage.

History holds only what was recorded in it. Conversations with your agent and data in other systems are not kept, unless they reach the playbook as a run's input or as an event. Auto hosts this history with your playbooks. For a self-hosted deployment, persistent storage and tested backups are part of the deployment plan; see the [self-hosting overview](https://on.auto/docs/self-host).

## Reading the history

Your agent can read where a run stands, the history of one run, the events of the whole playbook or one event in full. The same reads work over HTTP. Long histories come a page at a time, and a playbook stays readable after it is retired. The playbook's analytics sum up its runs over recent days, and they are current as soon as each run is recorded.

A run's record holds its result. What the run was given is on the first event of its history. The history keeps each event small, so a large value appears as its size until you read that one event in full.

In Studio, open Notifications from the bell to find requests waiting for you, failed runs and new comments. Open the Activity log to browse activity across playbooks and filter it by person, playbook or kind of activity. What you mark seen is saved for your account across devices. [The organization's activity](https://on.auto/docs/reference/http#the-organization-s-activity) describes the underlying reads and their fields.

[Inspecting a run](https://on.auto/docs/concepts/workflows#inspecting-a-run) says what a workflow run's history shows. [Run history and playbook events](https://on.auto/docs/reference/http#run-history-and-playbook-events) lists the reads and every event field, and the [MCP reference](https://on.auto/docs/reference/mcp#events-and-history) lists the tools your agent uses.

## Publishing events

A playbook's history can also hold what happened elsewhere, such as a month closed in the accounts or a deal won in a CRM. Your agent or another system publishes such an event, in the CloudEvents shape that many systems already send. The event then appears among the playbook's events, beside its definitions and runs.

An event is known by where it came from and its id. Publishing the same event again records nothing new, so a sender can safely try again. A published event cannot pass for one of the playbook's own records, such as a run that finished. [Publishing events](https://on.auto/docs/reference/http#publishing-events) gives the details.

## How events start work

What the playbook records can start work:

*   A workflow with an event trigger starts a run for each event that matches it. That can be a published event or one that another workflow recorded. It can also be one of the playbook's own records, such as a review that succeeded.
*   A run waiting for an event takes a matching one while it waits.

The playbook matches events in the order it recorded them. So the history explains each reaction: first the event, then the run it started, which names that event as its cause. When a trigger does not start a run, as when it reaches one of its limits, the playbook records that too. [Triggers](https://on.auto/docs/concepts/workflows#triggers) describes triggers.

Triggers, waiting runs and the folds of pages see a run only as the fact that it started and how it ended, with its result when it succeeded. They never see the run's input or its tool calls; those stay in the run's own history. [Events](https://on.auto/docs/reference/events) lists what each of these facts carries.

## Using history in later runs

A new run does not see earlier results by itself. A [lookup function](https://on.auto/docs/concepts/functions#lookup) can read the outputs of successful runs of one definition in the same playbook. For example, a workflow can collect this month's campaign reviews, then pass them to a reasoning function to identify recurring problems.

The lookup can filter by words in the output and by the date a run started. Its result says when older runs remain unread, so a workflow must not assume it has the complete history. [Reading the playbook's own runs](https://on.auto/docs/reference/lookup-format#reading-the-playbook-s-own-runs) gives the output fields and limits. You can also supply earlier results directly as a function's input.

## Dream (planned)

Dream is a planned feature, not available yet. It would revisit what a playbook has recorded and suggest ideas worth testing, such as a change to a method, for you to review. [Availability](https://on.auto/docs/concepts/functions#availability) lists it with the other planned features, and [Terminology](https://on.auto/docs/concepts/terminology) defines it.

## Sitemap

See the [full documentation and product sitemap](https://on.auto/sitemap.md) for related pages.
