Issue with Clay Not Retrieving 100% of Apify Results

Andi Deng · 2025-02-20 05:22:29.742187+00

Hey team, for some reason Clay isnt retriving 100% of the Apify results, can someone take a look? It happened a while back but was good till today. Here's the table if you need it:

Issue with Clay Not Retrieving 100% of Apify Results | Clay

14 comments

· Sorted by Oldest

Andi Deng
·
·
Another pull, 499 Apify results --> 366 Clay records, none should be duplicates (maybe single digits but definitely not 130 of them). Fresh Linkedin leads
Channeled
APP
·
·
There could be a few reasons why Clay isn't retrieving all 499 Apify results: 1. Record limit: Our Apify integration allows for retrieval of up to 5000 records from a single run. However, your Clay plan might have a lower limit on the number of records you can import per search. 2. Search parameters: Check if you've set any limits in your search parameters. You can control the number of records returned in your search by setting an overall limit (up to 50,000 records per search on most plans). 3. Duplicates: While you mentioned there shouldn't be many duplicates, Clay might be automatically removing some records it identifies as duplicates. To resolve this, try adjusting your search parameters and check your plan limits. If the issue persists, it may require further investigation by our team.
Sources: Pull Data from Apify Actor with Apify Find Company overview | Documentation | Clay University
Channeled
APP
·
·
Was that helpful?
Andi Deng
·
·
Channeled
APP
·
·
Was that helpful?
Channeled
APP
·
·
Hi Andi Deng! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Bo (Clay)
·
·
Hey - Sorry it's happening. Let's fix this. Can you let me know which specific source is experiencing this? I can see 5. Are you noticing any patterns in what's missing? For example, are certain tasks, actors, or types of data not appearing in your Clay results? Let me know the details! :)
(79 kB)
Andi Deng
·
·
hey thx Bo! it's really the first and second pull, 3-5 are duplicated pulls trying to pull additional records from same apify run so no worries. 1st and 2nd pull definitely have overlaps so probably deduplicated a lot. Might wanna just focus one 1st pull where Apify had 499 records and Clay only extract low 300s
Bo (Clay)
·
·
Hey! Looking at your pulls, I see different results between them. For the first pull (without any number), we found 149 results but only 134 made it to the table. For pull (1), we found 364 but only 321 are in the table most likely duplicates. I tried pulling without specifying a run, but that gave even fewer results (126). You can see this here: https://app.clay.com/workspaces/449716/workbooks/wb_u6yqT3UjukNw/tables/t_23gQeaNFx3TW/views/gv_SV74syRnj8pN Could you tell me exactly which Apify run we should be using? It might help if we create a fresh table for that specific run so we can properly analyze what's happening.
(17 kB)
Andi Deng
·
·
Hey Bo, nfoxlXfiqhBnsL1c0 For pull (1), we found 364 but only 321 are in the table most likely duplicates. ^that would be the run with 499 records in Apify
Andi Deng
·
·
Bo (Clay) hey Bo, newest Apify pull 1150 --> 600 results. Here's the table: https://app.clay.com/workspaces/449716/workbooks/wb_Et95Sh4sdePA/tables/t_oWFdB5bu5MUD/views/gv_DbiyeKi9FcWh Haven't touched it so you can take a look.
Bruno (Clay)
·
·
Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
🙏1
Bo (Clay)
·
·
I’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog. For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change. So what happens now? Now that your issue has been logged, I will tentatively mark this as closed. Please note that I will reach out to you as soon as I receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you. Do you have any further questions before I step away from this conversation until I have an update for you?

Andi Deng
·
·
Another pull, 499 Apify results --> 366 Clay records, none should be duplicates (maybe single digits but definitely not 130 of them). Fresh Linkedin leads
Channeled
APP
·
·
There could be a few reasons why Clay isn't retrieving all 499 Apify results: 1. Record limit: Our Apify integration allows for retrieval of up to 5000 records from a single run. However, your Clay plan might have a lower limit on the number of records you can import per search. 2. Search parameters: Check if you've set any limits in your search parameters. You can control the number of records returned in your search by setting an overall limit (up to 50,000 records per search on most plans). 3. Duplicates: While you mentioned there shouldn't be many duplicates, Clay might be automatically removing some records it identifies as duplicates. To resolve this, try adjusting your search parameters and check your plan limits. If the issue persists, it may require further investigation by our team.
Sources: Pull Data from Apify Actor with Apify Find Company overview | Documentation | Clay University
Channeled
APP
·
·
Was that helpful?
Andi Deng
·
·
Channeled
APP
·
·
Was that helpful?
Channeled
APP
·
·
Hi Andi Deng! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Bo (Clay)
·
·
Hey - Sorry it's happening. Let's fix this. Can you let me know which specific source is experiencing this? I can see 5. Are you noticing any patterns in what's missing? For example, are certain tasks, actors, or types of data not appearing in your Clay results? Let me know the details! :)
(79 kB)
Andi Deng
·
·
hey thx Bo! it's really the first and second pull, 3-5 are duplicated pulls trying to pull additional records from same apify run so no worries. 1st and 2nd pull definitely have overlaps so probably deduplicated a lot. Might wanna just focus one 1st pull where Apify had 499 records and Clay only extract low 300s
Bo (Clay)
·
·
Hey! Looking at your pulls, I see different results between them. For the first pull (without any number), we found 149 results but only 134 made it to the table. For pull (1), we found 364 but only 321 are in the table most likely duplicates. I tried pulling without specifying a run, but that gave even fewer results (126). You can see this here: https://app.clay.com/workspaces/449716/workbooks/wb_u6yqT3UjukNw/tables/t_23gQeaNFx3TW/views/gv_SV74syRnj8pN Could you tell me exactly which Apify run we should be using? It might help if we create a fresh table for that specific run so we can properly analyze what's happening.
(17 kB)
Andi Deng
·
·
Hey Bo, nfoxlXfiqhBnsL1c0 For pull (1), we found 364 but only 321 are in the table most likely duplicates. ^that would be the run with 499 records in Apify
Andi Deng
·
·
Bo (Clay) hey Bo, newest Apify pull 1150 --> 600 results. Here's the table: https://app.clay.com/workspaces/449716/workbooks/wb_Et95Sh4sdePA/tables/t_oWFdB5bu5MUD/views/gv_DbiyeKi9FcWh Haven't touched it so you can take a look.
Bruno (Clay)
·
·
Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
🙏1
Bo (Clay)
·
·
I’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog. For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change. So what happens now? Now that your issue has been logged, I will tentatively mark this as closed. Please note that I will reach out to you as soon as I receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you. Do you have any further questions before I step away from this conversation until I have an update for you?