In Airtable, an automation run is when the automation is triggered. So the number of actions in the automation doesn’t matter. Loops within an automation don’t matter. Note that if an automation is triggered, but no actions are run, it still counts towards your total. 

This is different from other automation systems. 

Thank you @kuovonne, this was what I kind of hoped for, but couldn't find a place to get it verified. I was a bit confused as you mention fx Make does not count by triggered runs alone.

So I guess it also means a trigger set for a scheduled time will always just consume one run regardless if there is zero records or thousands of records to do something to?

Hey @Kim_Trager1!

Re: So I guess it also means a trigger set for a scheduled time will always just consume one run regardless if there is zero records or thousands of records to do something to?

Correct. Such situation would consume one run, regardless of the amount of actions and records updated/created/found under such run. (as @kuovonne mentioned!)

You can also find more information and examples on Airtable automation limits here.

Mike, Consultant @ Automatic Nation

​@kuovonne ​@Mike_AutomaticN - Can you guys provide a link to any Airtable official documentation on automation limits? I’ve notice that my Repeating Groups show as separate runs for each record in my Automation History tab, and I think in turn each of those “runs” is counting towards my automation limit. 

​@JennJ 

The automation limits are currently published here: https://support.airtable.com/v1/docs/getting-started-with-airtable-automations

 

Thank you! Those footnotes always get me. One more qq - any chance you know if using a JavaScript code block extension also counts towards automations? I’m assuming no, since you’d be manually “triggering” the script. 

Running Scripting Extension does not count towards automations. Extensions (seen in the dashboard on the right side fly-out panel of a Data View) are completely separate from automations.