Docs › Automations
Run history and troubleshooting
See every time an automation ran, what each step did, and why it skipped or failed.
Experimental. Automations are still being tested. They may not run, or may give incomplete or wrong results — check anything important yourself, and tell us what goes wrong.
Every time an automation is set off, Daykite keeps a record. Open the automation, then choose Runs in the bar along the bottom to see them, newest first. The automations list shows how often each has run and when it last did.
Each run shows:
- Its result — Done, Skipped or Failed.
- When it ran, and what set it off (for example booking created).
- Open it for what each step did, in plain words — "Created the task "Prep for intro call with Tom Becker", due 2026-09-17.", "event.title contains "review" → yes", "Emailed tom.becker@example.com."
- The error, if it failed.
Runs only lists real runs. A Test run never did anything, so it's shown under Output instead and isn't kept here.
Skipped runs
A skipped run means the automation was set off, but didn't act — which is usually exactly right. The run says why:
| Message | Meaning |
|---|---|
| Skipped: it was a different meeting type. | The trigger is Only Intro call and someone booked a Design consultation |
| Skipped: it was in a different Space. | The trigger is limited to one Space |
| Skipped: it was in a different project. | The trigger is limited to one project |
| Skipped: it was a different routine. | The trigger is limited to one routine |
| Skipped: the title doesn't contain "Invoice". | The Only titles containing… setting didn't match |
| Skipped: it isn't ready — … | It was edited while on and a step was left half-finished; the rest of the message names it |
| Skipped: the workflow was switched off or deleted before it ran. | You switched it off a moment after it was set off |
| Skipped: what set it off no longer exists. | The task was deleted before the automation got to it |
An If step that answers no with nothing connected to no isn't a skip: the run is Done, and the steps on the other side are simply not reached.
Failed runs
A failed run means a step tried to act and something stopped it. The failed step is marked, and the reason is shown.
| Error | What to do |
|---|---|
| No address to send to — "{guest.email}" came out as "". | The trigger has no guest — use {guest.email} only with booking triggers |
| The list isn't in the task's project, so it can't be moved there. | Move the task to a list only works within the task's own project. Set the trigger to Only one project. |
| There's no task to move. | Move the task needs a task trigger |
| That webhook was deleted or switched off. | Choose another webhook, or switch it back on |
| Google Sheets isn't connected any more — reconnect it on Integrations. | Reconnect Google on Integrations |
| Interrupted before it finished. | Daykite was restarting. The run isn't retried, because its first steps may already have happened — check and finish by hand if needed. |
| Project not found. | The project a step adds tasks to was deleted, or you no longer have access — choose another |
When a step fails, the steps after it don't run. Steps before it have already happened.
Automations that never seem to run
- Is it On? A switched-off automation does nothing, and its runs aren't recorded.
- Does a Test run go the way you expect? If an If step answers the wrong way, change the input under Input and run the test again until it does.
- Is the thing happening to you? Automations react to your bookings, your events, tasks you created or were assigned, and your routines — see Whose automations run.
- Was it made by another automation? Things an automation creates never set off automations, so they can't loop.
- Is the feature switched on? Booking, task and routine triggers need their modules.