A practical field guide from Automation Ace.
Airtable Automation Not Running? How to Diagnose and Fix It
An Airtable automation that never runs gives you almost no feedback, which makes it feel unpredictable. In reality Airtable automations follow strict, knowable rules about when they fire, and a non-running automation is nearly always one of a few well-defined situations: it is turned off, its trigger condition is never actually met, it is watching the wrong view, or you have hit a plan limit. Work through these in order before rebuilding anything.
Confirm the automation is turned on and published
A newly built automation is off until you toggle it on, and edits require you to leave the editor for them to take effect. Open the automation, confirm the top toggle is on, and verify you tested the current version. An automation left in draft looks complete but never fires.
Understand exactly when your trigger fires
"When a record is created" fires only for genuinely new records, not existing ones. "When a record matches conditions" fires the moment a record first meets the conditions — and critically, it will not fire again for the same record until it stops matching and then matches again. "When a record enters a view" depends entirely on that view's filters. If your trigger is condition-based, confirm a record actually transitions into the matching state rather than being created already matching, which some setups miss.
Check the view the trigger watches
View-based triggers only see records that pass the view's filters and are not hidden. If someone edits the view's filter, sort, or hidden records, the automation's behavior changes without you touching the automation. Point the trigger at a dedicated, locked view used only by the automation so casual view edits cannot break it.
Look at the run history
Every automation has a run history panel. If it shows runs that failed, you have an action problem, not a trigger problem — expand the failed run to see the error. If it shows no runs at all, the trigger genuinely is not firing, which sends you back to the trigger-condition checks above.
Watch for run limits and timing
Airtable plans cap automation runs per month; once exhausted, automations stop until the cycle resets or you upgrade. Automations can also be throttled under heavy load, so a burst of changes may process with a delay rather than instantly. If runs simply stopped mid-month, check your usage against the plan limit first.
When the trigger is external
If you expect the automation to be kicked off by another tool, confirm the bridge is actually delivering. A common setup triggers Airtable from Zapier via webhook — verify that path with triggering an Airtable automation from a Zap. If your Airtable automations are load-bearing for operations and keep stalling, Automation Ace can audit and harden them.
Disclaimer: This article may include links to apps, products, or services. Some links may be affiliate links, which means Automation Ace may earn a commission at no extra cost to you.