Every playbook now has a Performance page that shows what it has actually done: how many times it ran, what succeeded, what failed, and who each email went to. This guide covers how to read that page and how to tell the difference between a playbook that is broken and one that simply has nothing to do.

<aside> 💡

Open Playbooks, find your playbook in the list, and click Performance.

</aside>

Opening the Performance page

The Performance button sits on every playbook card in the list, just below Edit.

Drafts do not have one. A draft has never fired, so there is nothing to show. The button is greyed out until you finish setting the playbook up and turn it on.

The four numbers at the top

Tile What it counts
Executions Times the playbook ran and did something
Succeeded Runs where every step worked
Failed Runs where at least one step did not work
Last Run When the playbook most recently did something, or Never

Two things about Executions surprise people, so read this part carefully.

<aside> ⚠️

Executions counts times the playbook acted, not times the trigger fired. If your playbook has conditions (only jobs over $80,000, only employers in Texas), every firing that fails those conditions is filtered out and never appears here. A low number usually means your conditions are narrow, not that the playbook is broken.

</aside>

And Succeeded plus Failed always adds up to Executions, because there are only two outcomes. A run counts as failed if even one of its steps failed, even when the other steps worked fine.

The chart

The bar chart shows runs per day across the window you picked, stacked by outcome: green for succeeded, red for failed. Days with no runs show as gaps at zero.

Use it to spot the shape of a problem. A wall of red starting on one particular day usually points at something that changed that day, like a webhook endpoint going offline or a connected mailing list being deleted.

Choosing a time range

The dropdown at the top right offers Last 7 days, Last 14 days, Last 30 days, Last 90 days, This month, Last month, and Custom range. The page opens on Last 30 days.

<aside> ⚠️

Run history is kept for 90 days. Anything older is deleted automatically. You cannot pick a start date beyond that window, and a custom range cannot span more than 90 days.

</aside>

Also worth knowing: history starts the day this update went live. Runs from before that were never recorded, so an old playbook will look like it just started working. That is expected and it is not something we can backfill.

Reading the activity list

Below the chart is the run history, newest first, ten per page. Each row is one step of one run.

Column What it shows
Date When the run happened
Step Which action ran (Send Email, Send Webhook, and so on)
Sent To The recipient, record, or destination the step acted on
Status Whether the step worked