Issues with Clay's Auto Source Run: Exceeding Row Limits Explained

Bhanu S. · 2025-07-10T09:32:56.576Z

Hi, I'm encountering an issue with Clay's auto source run in the table `" "`. Our plan allows up to 25k rows, and currently, the table has around 15k rows. However, when I try to run the source to add more data, I receive the following error: "Your source has exceeded your plan limit of 25k." Could you please help me understand why this is happening?

Issues with Clay's Auto Source Run: Exceeding Row Limits Explained | Clay

8 comments

· Sorted by Oldest

Bhanu S.
·
·
Clay
APP
·
·
The "25k" limit refers to searches per query, not table rows. Your Pro plan allows up to 25,000 searches per query when running sources. Even though your table has 15k rows, if your source is configured to search for more than 25k records in a single run, it will hit this limit. Try running your source in smaller batches or adjust your source filters to stay within the 25k search limit per query.
Source: Clay Plan Feature Overviews
Clay
APP
·
·
The 25k limit refers to the number of records your source attempts to search/process in a single run, not your table's row count. Even with 15k existing rows, if your source is configured to pull more than 25k records, it will hit this limit. To resolve this, try processing data in smaller batches (like 200-500 rows at a time) to stay within the limit and control which rows to process. You can also adjust your source filters to reduce the total number of records being searched.
Sources: Apollo.io integration overview | Documentation | Clay University Apollo.io integration overview | Documentation | Clay University
Daniela D.
·
·
Hey Bhanu! Thanks for reaching out. Happy to help✨. Could you confirm if any modifications were made to the source/results imported? Ex: Were more records previously imported and subsequently deleted? Was the import limit higher than 10k?
Bhanu S.
·
·
Hi Daniela D., Previously there were 31k records in total. Then we turned on auto-delete, and now it’s stuck at 15k. Regarding the modification of the source: we tried changing the limit from 25k to 10k in the source, but it didn’t work. We also tried adding just 300 new records, but that didn’t work either.
Bo (.
·
·
Hey, even with auto-delete enabled, deleted rows still count toward your plan’s row limit. So if your table previously had 31,000 rows and you’re on a 25,000 row plan, the system still treats it as over the limit, even if only 15,000 remain visible. To move forward, you’ll need to create a new table—this resets the count and avoids the stuck state. Let me know if you have more questions.
Siddhant B.
·
·
This is counter intuitive... So there is a 25k hard limit, which when reached prevents further data from coming into the system? So even if I had set a limit of 5k, imported 5k, deleted ALL rows, I can only do this 4 times before new data cannot be imported?
Munnawar H.
·
·
Hi Bhanu, Thank you for following up. Yes, your assumption is correct, and this is something we’ve received feedback on and are actively working on improving. I’ll make sure to pass your feedback along to our product team as well.

Bhanu S.
·
·
Clay
APP
·
·
The "25k" limit refers to searches per query, not table rows. Your Pro plan allows up to 25,000 searches per query when running sources. Even though your table has 15k rows, if your source is configured to search for more than 25k records in a single run, it will hit this limit. Try running your source in smaller batches or adjust your source filters to stay within the 25k search limit per query.
Source: Clay Plan Feature Overviews
Clay
APP
·
·
The 25k limit refers to the number of records your source attempts to search/process in a single run, not your table's row count. Even with 15k existing rows, if your source is configured to pull more than 25k records, it will hit this limit. To resolve this, try processing data in smaller batches (like 200-500 rows at a time) to stay within the limit and control which rows to process. You can also adjust your source filters to reduce the total number of records being searched.
Sources: Apollo.io integration overview | Documentation | Clay University Apollo.io integration overview | Documentation | Clay University
Daniela D.
·
·
Hey Bhanu! Thanks for reaching out. Happy to help✨. Could you confirm if any modifications were made to the source/results imported? Ex: Were more records previously imported and subsequently deleted? Was the import limit higher than 10k?
Bhanu S.
·
·
Hi Daniela D., Previously there were 31k records in total. Then we turned on auto-delete, and now it’s stuck at 15k. Regarding the modification of the source: we tried changing the limit from 25k to 10k in the source, but it didn’t work. We also tried adding just 300 new records, but that didn’t work either.
Bo (.
·
·
Hey, even with auto-delete enabled, deleted rows still count toward your plan’s row limit. So if your table previously had 31,000 rows and you’re on a 25,000 row plan, the system still treats it as over the limit, even if only 15,000 remain visible. To move forward, you’ll need to create a new table—this resets the count and avoids the stuck state. Let me know if you have more questions.
Siddhant B.
·
·
This is counter intuitive... So there is a 25k hard limit, which when reached prevents further data from coming into the system? So even if I had set a limit of 5k, imported 5k, deleted ALL rows, I can only do this 4 times before new data cannot be imported?
Munnawar H.
·
·
Hi Bhanu, Thank you for following up. Yes, your assumption is correct, and this is something we’ve received feedback on and are actively working on improving. I’ll make sure to pass your feedback along to our product team as well.