Automation Answers

Why Is My Airtable Automation Not Running?

Diagnose an Airtable automation that does not fire by validating trigger conditions, views, permissions, run history, and test records.

By Automation Ace Editorial TeamReviewed for technical accuracy by Troy TessalonePublished Updated

Short answer

Why Is My Airtable Automation Not Running?

An Airtable automation usually does not run because it is off, its record never newly meets the trigger conditions, the selected view or fields changed, or the automation exceeded a workspace limit. Confirm the automation is on, create or update a fresh record so it crosses the trigger condition after activation, review run history, and retest each action with the intended account permissions.

Common causes

  • The automation is off, or changes were not tested and enabled.
  • The record already matched when the automation was activated and never crossed into the trigger state again.
  • A filtered view, field name, table, or condition changed.
  • The automation ran but an action failed because of permissions or missing values.
  • Workspace run limits or platform incidents prevent further processing.

Diagnostic steps

  1. Verify the automation toggle and confirm you are in the intended base and workspace.
  2. Read the trigger literally and note whether it requires creation, update, view entry, or condition matching.
  3. Create a fresh test record or move one from non-matching to matching after the automation is on.
  4. Review run history for the exact record and timestamp; open every failed action.
  5. Check renamed fields, deleted views, blank required inputs, and collaborator permissions.
  6. Review workspace usage and Airtable status before rebuilding the automation.

Example

An automation triggers when a record enters “Ready to send.” Records already in that state before activation do not create a new transition. Change a test record to “Draft,” save it, then change it to “Ready to send” to produce a valid new event.

Caveats

Trigger behavior differs among “record created,” “record updated,” “enters view,” and “matches conditions.” Tests in the builder do not prove that future records will cross the live trigger. Avoid modifying production records solely to retest if downstream email, billing, or deletion actions are enabled.