Skip to main content

See screenshots below - I've used the "find records" option many times, and always restrict it to a specific view.  Only this time, and any time I test the find records action anywhere globally, it suddenly seems to stop at 10 records. 

The description still lists the limit as 100 records, it just stops at 10.  The view in question has 52 records in it. I've even went so far as to test this on older automations which we've since stopped using (afraid to touch any currently running automations for fear they might stop working properly).

I've recreated the automation, refreshed the page, re-sorted/grouped records, but have not been able to work around the issue.

Has anyone else ran into this?

2025 Update:

This seemed to be a bug back in 2024 which is now fixed.

However, if you're still having this problem, It's possible that you're simply trying to test or preview your automation from the Automations screen itself.

During a test of an automation or a preview of an automation, Airtable will only find a maximum of 10 records during all the tests & previews.

However, once you actually trigger the automation and it runs all on its own, it will find all of your records for you.

Also, for more advanced automations (with tests that will run on all of your found records), you may want to use Make’s advanced Airtable automationsIf you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread. For example, here is how you would instantly trigger a Make automation from Airtable.

Hope this helps! If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld


2025 Update:

This seemed to be a bug back in 2024 which is now fixed.

However, if you're still having this problem, It's possible that you're simply trying to test or preview your automation from the Automations screen itself.

During a test of an automation or a preview of an automation, Airtable will only find a maximum of 10 records during all the tests & previews.

However, once you actually trigger the automation and it runs all on its own, it will find all of your records for you.

Also, for more advanced automations (with tests that will run on all of your found records), you may want to use Make’s advanced Airtable automationsIf you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread. For example, here is how you would instantly trigger a Make automation from Airtable.

Hope this helps! If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld


Already done - sent it in earlier this morning.  Glad it's not just me.

 

Funny you mention it though, my next action was embedding the records in an email.  Thanks for the assistance!


Already done - sent it in earlier this morning.  Glad it's not just me.

 

Funny you mention it though, my next action was embedding the records in an email.  Thanks for the assistance!


I am experiencing the same behavior FWIW


2025 Update:

This seemed to be a bug back in 2024 which is now fixed.

However, if you're still having this problem, It's possible that you're simply trying to test or preview your automation from the Automations screen itself.

During a test of an automation or a preview of an automation, Airtable will only find a maximum of 10 records during all the tests & previews.

However, once you actually trigger the automation and it runs all on its own, it will find all of your records for you.

Also, for more advanced automations (with tests that will run on all of your found records), you may want to use Make’s advanced Airtable automationsIf you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread. For example, here is how you would instantly trigger a Make automation from Airtable.

Hope this helps! If you’d like to hire the best Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld


I got an update from Airtable support.  They've limited testing (temporarily) to 10 records while their developers are working on enhancing the find records automation to go beyond the 100 record limit.

I have been advised that any test of the automation will always return 10 records, as will any subsequent test of automations relying on the find records automation.  This includes not just testing individual steps, but hitting the "test automation" button (I frequently use this to send/resend reports as needed).

That being said, actual automation runs seem to be working properly as of now.


I am experiencing the same behavior FWIW


See my reply to solution above - I got a response from Airtable developers on the matter.


is anyone still having this issue (other than me?) I can't seem to get it to return more than 10 records. 


+1 here on still having issues


Hi all - I’ve figured it out as I had this same issue

the scheduled trigger will only fire when the inputted time and date are in the future and when the date and time run, the automation will run correctly from start to finish and output more than 10 records (if there are 10 records as a result of either the View or Conditions in the Find Records)

I set all of my automations with this trigger up to fire at 6:15pm last night and ensured they were all turned ON prior to firing and everything was correct. They all ran perfectly. 


Hi all - I’ve figured it out as I had this same issue

the scheduled trigger will only fire when the inputted time and date are in the future and when the date and time run, the automation will run correctly from start to finish and output more than 10 records (if there are 10 records as a result of either the View or Conditions in the Find Records)

I set all of my automations with this trigger up to fire at 6:15pm last night and ensured they were all turned ON prior to firing and everything was correct. They all ran perfectly. 

Ignore me here, not enough coffee this morning and did not see the 2025 update at the top.

 


Reply