Help for owners
My Airtable automations stopped running or keep failing
Short answer
Airtable counts a run each time a trigger fires, and failed runs count as well as successful ones. Allowances are per workspace per month and reset on the first day of the month. Open the automation's run history, filter by failed, and read the failing step. A noisy trigger can use up a month's runs on its own.
Does this sound like your situation?
- An automation that worked last week does nothing now.
- Airtable says my automation runs for the month are used up.
- Emails or records that an automation should create are missing.
- Failure emails go to one person who has left or never reads them.
- I cannot turn on a new automation because the base has too many.
Why does this happen?
Failed runs use up the monthly allowance
Airtable counts a run each time a trigger fires, and both failed and successful attempts count. An automation that fails and retries on every record edit can consume a large part of the allowance without doing any useful work. The limits are per workspace and reset on the first day of each month.
Confirmed by support.airtable.com
The number of automations per base is capped
The cap counts every automation in the base, including ones that are turned off. Turning one off does not free a slot; deleting it does.
Confirmed by support.airtable.com
Failure notices go to one person
Airtable sends failure notifications to the last user who enabled the automation. If that person left the company or filtered the emails away, failures go unseen for weeks.
Confirmed by support.airtable.com
Some actions depend on the plan
Run a script is not available on the Free plan, and on Free the email action can only reach base collaborators. Team and Business plans cap the number of unique outside email addresses per day.
Confirmed by support.airtable.com
The data changed under the automation
Someone renamed a field, changed a field type or removed a linked record, and the step that used it now fails. The run history shows the failing step.
What can I do about it today?
- Open the run history and filter by failedIn the automation, Run History lets you filter by succeeded, failed or canceled and expand a run to see the failing step. Take a screenshot of the first failure.
- Check the trigger for a runawayIf one automation has thousands of runs this month, its trigger is firing far more often than intended. Pause that one automation rather than all of them.
- Find out who gets the failure emailsCheck who last enabled each important automation, and ask them to look in their inbox and spam.
- Do not delete automations to free space yetDeleting is permanent. Write down what each one does first, and export the base as a backup.
- Note what must happen by hand until it is fixedWrite the one or two tasks the automation did, so someone does them manually in the meantime.
When should I bring someone in?
- The automation sends invoices, orders or customer messages and failures cost you money.
- You are repeatedly at the run limit and the only advice is a bigger plan.
- Nobody knows what half the automations in the base do.
How do I handle it?
- Read the history, not the symptomsI go through failed and canceled runs to find the first failure and the shared cause, such as a changed field or a bad trigger.
- Check what each automation costsI count runs per automation so the few that burn the allowance are fixed first.
- Add a way to notice failuresFailure notices are sent to a shared mailbox or channel rather than one person.
- Decide what belongs outside AirtableHeavy or high-volume jobs may belong in a small script or service with logging and retries. Light ones stay where they are.
- Test with copies of real recordsChanges are checked on a copy of the base before they touch your live one.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Do failed automation runs count against my limit?
Yes. Airtable states that both failed and successful automation attempts count against the allowance.
When does the run count reset?
Airtable states that automation run limits reset on the first day of each month.
Does turning off an automation free a slot?
No. Airtable states that turned-off automations still count towards the per-base limit, and only deleting one frees a slot.
Is moving to a bigger plan the only way to get more runs?
Airtable names moving to a higher plan as the standard way. Reducing wasted runs from broken or noisy triggers can also bring you back under the allowance.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.