I have an automation that runs based on the trigger, when a record is created. This automation runs perfectly in all tests.
However, when I run a process that creates 5-10 records within 2 minutes, the automation does not run for all records. This clearly tells me that the Airtable infrastructure cannot handle even the smallest volume. This is deeply concerning. I would not expect an automation to run into volume issues until the volume was over 1000 a minute.
Has anyone else seen this similar poor performance from Airtable interfaces?
Automation not running despite conditions being met and tests being successful
+2
+31I can't say I've ever encountered this issue myself. Here's a gif of an automation with "When a record is created" as a trigger running for 20+ records created in 2 seconds:
Given that you've checked your automation setup and are still facing issues I'd suggest opening a ticket with support to see if they can help you troubleshoot this
+29Airtable was not designed to support creating 1000+ records per minute. When I have created records at that rate (usually via scripting), Airtable usually struggles a bit.
However, I have not had problems with automations when creating 5-10 records in 2 minutes. Sometimes automations are a little slow to trigger and a little slow to run, but they eventually run. You can see when the automation has been triggered by looking at the automation history. When an automation is triggered multiple times in a short period of time, there may be multiple "in progress" automation runs.
Depending on your subscription plan, you may also have run out of automation runs for the month.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.