Clay Issues: Long Running Rows and Bugs Reported

John D. · 2025-12-08T17:27:07.608Z

Hello, Is anybody experiencing clay issue/bugs right now? most of our rows have been running for the past 20+mins already

Clay Issues: Long Running Rows and Bugs Reported | Clay

Clay Support
APP
·
·
That's frustrating—let me help fix this. Rows running for 20+ minutes usually indicates a processing issue.
Try this first:
Click the column header of stuck columns
Hover over "Run column"
Select "Force" to jump start the run
If that doesn't work, try a hard refresh:
Mac: Cmd + Shift + R
Windows: Ctrl + Shift + R
This could also be an infinite loop if you see credits depleting rapidly or the same enrichments running repeatedly on the same rows. [1] Performance issues are more common with larger tables or complex workflows.
Let me know if the force run helps!
Clay Support
APP
·
·
Was that helpful?
John D.
·
·
nope. could you forward me to a clay live support?
Clay Support
APP
·
·
I understand your frustration, and I’ll connect you to a human agent who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
John D.
·
·
https://app.clay.com/workspaces/42993/workbooks/wb_0t5km3syPmFkm5kcTWk/tables/t_0t6ycmr5owKUsVHr9rz/views/gv_0t5mmpdwqMv73YF4R8b
John D.
·
·
this is our clay workspace and its running for 15+ minutes when I took a screenshot but its already running for 20-30+ mins already
Luca P.
·
·
Hi John, thanks for reaching out to support!
Let me take a quick look at your table here to see what is going on
Luca P.
·
·
I just took a look at the table, and it seems like all the rows executed properly. Are you still experiencing this issue?
John D.
·
·
yes it went back to normal and now again it takes too much time to give out result
John D.
·
·
John D.
·
·
its even running for 47 mins already
Luca P.
·
·
Hi, this is an issue that we have identified that we are experiencing with out AI columns. Our engineering team is hard at work on this and should have a fix being deployed soon. We will let you know when we have any updates!
John D.
·
·
Okay I hope it gets fixed today! We are encountering another issue where all the outputs the column gives out is "unable to access linkedin"
Luca P.
·
·
Hi! I took a look into the error you're seeing, and the issue isn’t coming from Clay — it’s coming from Prospeo’s side. When Clay sends the request to Prospeo’s API, their Cloudflare security firewall is blocking the traffic before it reaches the actual Prospeo endpoint. This results in the “403 Forbidden” page you’re seeing.
To resolve this, Prospeo will need to update their Cloudflare settings to allow requests coming from Clay’s servers. If you reach out to Prospeo support, you can share the following details to help them identify the block:
Endpoint being called: POST https://api.prospeo.io/domain-search
Source IP being blocked: 34.237.138.127
Cloudflare Ray ID: 9ab43465dc0bc5af
Timestamp of request: 2025-12-09T11:36:25Z
Once Prospeo whitelists our IP (or adjusts their WAF rules), your enrichment will run normally. Let us know if you'd like us to confirm the fix on our end — happy to help!

36 comments