Appearance
Run History and Troubleshooting
Every time an automation runs, PodcasterPlus records what happened. The Execution History page is where you check that runs went out, see exactly what each step did, and work out why something didn't.
To get there, go to Automations in your podcast's sidebar and click History. Use Refresh to pull in the latest runs.
Filter the list
Two funnels narrow the table:
- Status: All, Completed, Failed, Pending, Processing, or Skipped
- Automation: All Automations, or one specific automation
The table shows 50 runs per page, with Previous and Next below it.
Read the table
| Column | What it shows |
|---|---|
| Status | The run's outcome (see below) |
| Automation | Which automation ran |
| Trigger | The event that started it, like Booking Confirmed |
| Started At | When the run began |
| Duration | How long it took |
| Actions | A Details button for the full breakdown |
What each status means
- Pending: queued and waiting to run
- Processing: running right now
- Completed: every step finished
- Failed: something went wrong. Open Details to see the error
- Skipped: the run didn't execute because a monthly plan allowance was already used up
Open the Details dialog
Click Details on any run to open Execution Details:
- Status and trigger at the top
- Started and Completed timestamps
- Error: the error message, when the run failed
- Context Data: the information the run carried, which is what magic tags resolved from
- Action Results: a step-by-step record of what each action did
Branch skips are normal
When a run includes a condition, the steps on the branch that wasn't taken show as skipped in Action Results. That's the condition doing its job, not a problem.
Understand skipped runs
Plans include monthly allowances for the things automations consume: automation runs, email sends, webhook sends, notification deliveries, and AI credits. When one is used up, related work is skipped instead of run:
- If the automation runs allowance is used, the whole run is skipped.
- If a specific allowance like email sends or webhook sends is used, just those actions are skipped and the rest of the run continues.
Skipped runs are never silent. The History table flags them with a "Quota reached" note naming the allowance, and the Details dialog explains which actions were affected, with an Upgrade plan button.
Skipped runs and actions don't retry. Allowances reset on the 1st of each month, or you can upgrade to raise them. See Plan Limits.
Troubleshoot a failed run
- Filter Status to Failed and open Details on the run
- Read Error for the headline, and Action Results to see which step broke
- Check Context Data if magic tags came out empty: the tag's record (guest, booking, or episode) may not have been part of that run
- Fix the step in the flow builder, for example a mistyped webhook URL or a send-email step with no template selected
- Save, then use the Test button to run it again and confirm the fix here in History
If an automation isn't running at all, check its switch on the Automations page first: disabled automations never run.
What's Next?
- Adjust your automations in the flow builder
- Check your plan's allowances
- Review your templates if emails aren't reading right