Debugging automations
Open the automation and read its Activity log under the canvas. Each entry is one item the automation processed, with the resolved case ID and any error. Almost every "why didn't this fire?" question is answered there.
Last updated
Open the automation and read its Activity log under the canvas. Each entry is one item the automation processed, with the resolved case ID and any error. Almost every "why didn't this fire?" question is answered there.
What you need
- Edit access to the automation (the creator, or a workspace owner if it's an orphaned automation).
What the Activity log shows
Each entry is timestamped and color-coded by outcome:
- Processed — the file was ingested and (if extraction was on) extracted. Detail line shows the file count and whether extraction ran.
- Skipped — the trigger matched, but the run intentionally stopped (most often a duplicate the automation was set to skip).
- Error — the run failed at one of the steps. The summary names the step.
Recent runs only — older history rotates out. If you need to debug something old, reproduce it with a fresh test message or file.
Common debugging patterns
Automation isn't firing at all
- Check the toggle on the card.
- Check for an Auto-paused chip and read the banner — it tells you exactly which integration to reconnect or whose access expired.
- Check Settings → Integrations for the underlying connection.
- Check the trigger filters. For Gmail labels, the match is exact — a renamed label won't match the old name. For Drive, the match is on the folder you specified, not its subfolders.
Items match but the case doesn't appear
- Open the Activity log and find the entry for that item.
- Read the summary. If it says Skipped, your duplicate-handling setting may be set to Skip duplicate while the source has come in before.
- If it says Error, the message names the step that broke. The two most common causes: the destination category can't be resolved (no Extract template and no Destination category), or extraction failed on the file itself.
Wrong mailbox or wrong category
Open the automation. Mailbox lives on the Destination node. Category is on the Destination node when extraction is off, or comes from the Extract template's linked source when extraction is on — switch the template (or the source on a multi-source template) to change it.