Best answer

Code by Zapier Behavior Not Running for All Data Rows

  • 9 February 2021
  • 4 replies


I’m looking for guidance on a Zap I built to filter data in Airtable and send SMS texts to relevant individuals (based on day of week). There are 219 rows of data in my Airtable. For background -  due to a lack of native spreadsheet filter action, I had to use Code by Zapier to fork the data (for each row of the spreadsheet) in Airtable and Filter by Zapier to identify per each row if it fit the specifications (day of week). 

My Zap should run for each record that exists in Airtable (219) and filter for the day (ex/ Monday) and then send a text in Twilio. It ran successfully with 2 errors that are easy to fix. However, I'm seeing in my Zap History that it only had 100 runs of my automation and only identified 39 records with the filter of Monday. There should have been 219 runs of my automation (each row in Airtable) with 79 successful runs for the Monday filter and 140 filtered out records.

I read about limits for Code by Zapier actions before I went live and it said:

  • 250 forks for an individual automation run (under that limit at 219)
  • 10 second run time (Help article indicates if this limit was met, I would see an error relating to that - no error was presented)
  • 265 MB of memory limit for code steps (Help article indicates if this limit was met, I would see an error relating to that - no error was presented)

It doesn’t seem that I’m running into limits based on my research. Does anyone have any idea what could be causing this issue? My preference is to not run every single row via forking and allow for an upfront filtering mechanism. Since that’s not an option in Zapier, I went down the forking route.


Thanks in advance!


Best answer by GetUWired 9 February 2021, 20:30

View original

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

4 replies

Userlevel 7
Badge +14

Hi @chicagolights 

Rate limits and throttling in Zapier

Check this help article:

Believe you can reach out to Zapier support to raise this threshold:

Userlevel 7
Badge +12


How are you pulling the rows from Airtable? If you are pulling your records with the Airtable API the max records returned by default is 100 which might explain why it ran 100 times. 

If you are using the api, it might be worth setting up different views in Airtable for the different days of the week then in your code if it is monday you could just pull all the records associated with the monday view. 

@GetUWired - that’s exactly it, I was pulling via API from Airtable. So the limits were related to Airtable API vs Zapier forking limits. That’s very helpful, thank you!

Userlevel 7
Badge +12


Always happy to help! Happy Zapping!