How do I track automation events and fix ones that didn't send?
Read the status dots on a client's calendar, understand what each one means, and work out why an event errored or arrived silently.
Every scheduled automation event on a client's profile Calendar tab carries a status dot. That's where you check whether an event fired, and the first place to look when a client says they didn't get something.
Turn the Automations toggle on in the calendar filters if events aren't showing.
What each automation event status means
| Status | Meaning |
|---|---|
| Pending (gray) | Scheduled, hasn't fired yet |
| Running (blue) | Firing right now |
| Done (green) | Fired successfully |
| Error (red) | Fired but something failed — for example, the linked content had been deleted before the event ran |
| Canceled (gray) | Removed or disabled before it fired — nothing was sent |
Fix an event that ended in error
An error means the event fired but couldn't complete, most often because the content it pointed at had been deleted since the automation was built.
- Click the event to see which content it was meant to deliver.
- Assign that content to the client manually — the errored event can't be re-run.
- Open the automation in the editor and point the event at content that still exists, so future clients don't hit the same error.
Work out why a client didn't get a push notification
The usual reason is that the client has no device registered for push notifications — they haven't installed the client app, or they declined notification permission.
Why an assignment arrived without a notification
By design. Content events — programs, meal plans, forms, and vault items — assign silently, so the content simply appears in the client app with no "you've been assigned" notification. Form events don't send an immediate assignment notification either, though a form with reminders enabled still sends its scheduled reminders.
If you want the client told, add an Automated Message or In-App Notification event on the same day as the assignment.
Things to watch out for
Automated messages are sent as normal chat messages from whoever scheduled the event, so the client can't tell an automation sent it. There's no separate automated message type.
Events run in the client's timezone, not yours. If an event looks late or early, check the client's timezone before assuming something failed.
Editing the automation template doesn't touch events already scheduled on clients — those are snapshots taken at assignment. To change what's coming for one client, edit the pending events on their Calendar tab.
Deleting an automation doesn't cancel anything. Events already scheduled on clients keep running, and you cancel them one at a time from each client's Calendar tab.
On a team, the Automations and Onboarding lists only show a team member the automations and flows they created unless they have the view-all-team-resources permission, and can only cancel or edit events for clients assigned to them.