Clay S. Clay has been ultra buggy for us the past few weeks. Always stops randomly when importing rows. Anyone encountering similar issues? Any way to fix this? Import UI claims 21k rows where imported when really only 7k end up in the table etc.
The discrepancy between displayed and actual imported rows often occurs due to applied limits in search filters (like restricting leads per company) or loading delays with larger tables. To fix random stopping and import issues: • Force refresh: Try Command/Ctrl + Shift + R to resolve performance issues • Force run columns: Click the column header → hover over "Run column" → select "Force" to restart stuck processes • Create fresh columns: If columns remain stuck, delete affected columns and create new ones, then re-map your data • Check filter limits: Review your search filter settings and adjust any applied restrictions before importing These steps address common causes of import interruptions and row count discrepancies.
lol this is a bug not an error on our side
impossible to get a reply from a human it seems
what happened to clay support? Just useless AI or do they still employ any humans that can help?
Hi Jakob, We appreciate your patience as we experience a high volume of tickets. I'm happy to take a further look at this now. Do you have any more context you'd like to add to the issue you're experiencing? -Nicole
Hi Jakob, So just to ensure I have a full understanding of your issue, your interface is showcasing that 21k rows were imported when only 7k rows were? I took a deeper look at your table and it seems like the interface is displaying that 7,544 imports have occurred. Did you only experience this issue in the initial import stage, or is this something you continue to experience on your end? -Nicole
I imported two sources
in total there should be 30k+ rows
but it just stopped after 7k as you can see in the screenshot
this is a bug and we cannot use clay until it is fixed
Hi Jakob, Thank you for providing that additional context. I have taken a deep look into your account and I think the issue is stemming from the fact that you are currently on the free plan. This is limiting the amount of imports possible. I also see you have around 200 credits which will make it difficult to take further actions with so much data. I would recommend upgrading to a starter or explorer plan to maximize your workflows. -Nicole
lol what
I'm not on the free plan
been paying for clay for ages
but the number of bugs and the level of support shown here make me question it
Hello Jakob! Jumping in for Nicole here. Apologies for the experience you have been having so far. Customer experience is top of mind for us. Give me a moment while I catch up on the issue and help you out here!
Also to confirm I believe we have two tickets open with you. I am going to go ahead and close the other one out to ensure we are tackling an issue in one ticket and avoid any confusion!
I dont quite understand the explanation. This is obviously a bug no? Just looking at the screenshot below you can see that there should be more than 30k rows in the table but only 7k exists. I never deleted any rows.
also I just did what you told me, and it AGAIN stopped at 7k rows
Hi, Yes, this is a bug. Our team is investigating and we’ll update you as soon as we have more information. Sorry about the trouble this has caused. Let me know if you have more questions.
any update?
Hi, there’s no update yet. Our engineers are still working on it, and we’ll let you know as soon as we have more information. Some users have been able to work around the issue by creating a new table, but we’ll keep you posted once there’s a proper fix. Let me know if you have more questions.
any update now?
still no update?
Kareem Amin please have a look at this thread. The level of support demonstrated here is seriously concerning
Hi Jakob - understand the frustration here. The engineering team is working on the issue and you'll hear back from us here when this is solved.
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.
lol what? The problem is not solved. You can check the table. If you do this you will see that absolutely NOTHING has changed.
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
any update then?
Hey Jakob - George here, I head up the support team - happy to take it from there. I'm still working on getting up to speed and will circle back as soon as we know more. I also sent you a DM on Slack too.
Hey Jakob - I think we found the issue here - do you mind if I re-run that source to see if all of the rows come in? If that works, I can provide more details on what we found, but just want to verify first.
I've run the two sources again and no new rows where added
Hey Jakob - closing out this thread too - I dm'd you so if anything else comes up, feel free to flag it there!
.png){kind=logo}
