John D.

Commented on Post on Nov 14, 2025·Posted inClay Support

John D.

Could you let me know if ever this issue gets resolved Thanks!

Commented on Post on Nov 14, 2025·Posted inClay Support

John D.

Nope, I cleared my browser's cache and refreshing the page still it shows an error

Posted in Clay Support·

John D.

Post on Nov 14, 2025

I am having trouble adding a template. It gives me error when clicking the specific template that I want. I did this process yesterday and it was working alright but now it doesn't. Any issues happening on the back end that I don't know?

2 attachments

9Comments

Commented on Critical Issue: High Failure Rate in Claygent AI L...·Posted inClay Support

John D.

Alright thank you for that update

Commented on Critical Issue: High Failure Rate in Claygent AI L...·Posted inClay Support

John D.

Hello Sayli G., Any updates regarding this issue?

Commented on Critical Issue: High Failure Rate in Claygent AI L...·Posted inClay Support

John D.

Thanks for getting back to us and for looping in the engineering team. Here is the additional context you requested:

1.
When did this start happening? We first noticed this significant increase in the failure rate approximately two weeks ago.
2.
Confirmation of API Charges: My apologies for the earlier confusion on this point. I can now definitively confirm that yes, we are being charged an API call for every row that returns the "Unable to Verify" error. My initial assumption was incorrect. This reinforces our belief that Clay is successfully passing something to our API, but the data being passed is unusable, causing the call to fail and waste our credits.
3.
Comparative Table URL: Unfortunately, we do not have a preserved "before" state of the tables. As a standard part of our operational workflow, we clear out old, processed data from our tables to stay within our 50,000-row limit. But those are the same tables we ran before having this error

Commented on Critical Issue: High Failure Rate in Claygent AI L...·Posted inClay Support

John D.

To answer your other questions:

1.
Yes, these exact workflows and prompts were working with a very high success rate until recently. This is a new and sudden degradation in performance.
2.
Here are the URL links for the tables

https://app.clay.com/workspaces/42993/workbooks/wb_0swzkc7x7XNzRN2Sm7z/tables/t_0t2bxm7CTbTtie53uaT/views/gv_0sy2t0174mntNokBUB4 https://app.clay.com/workspaces/42993/workbooks/wb_0swmxk1MaRjSRBRunm6/tables/t_0t432gyRsG6bxn8WuZj/views/gv_uuYKwiKmbdE3 https://app.clay.com/workspaces/42993/workbooks/wb_0t0isfaNa42TQw9vv5G/tables/t_0t3248fHrB2hgF9iW42/views/gv_uuYKwiKmbdE3 https://app.clay.com/workspaces/42993/workbooks/wb_0syvi5kh3fFdsUrwEVD/tables/t_0t3q7aznFStk4xw6TZo/views/gv_0sy2t0174mntNokBUB4 Given that we are paying for API calls that are failing due to the poor quality of the scraped data, this strongly points to an issue with the reliability of your data retrieval step. Please proceed with looping in an engineer to investigate why the LinkedIn scraper is now consistently returning bad data.

Commented on Critical Issue: High Failure Rate in Claygent AI L...·Posted inClay Support

John D.

Hi Clay Support Team, I am formally requesting to be connected with a live support agent or a technical specialist to discuss a high-priority issue. We have been corresponding with your automated support system, but the generic troubleshooting steps provided are not applicable to our situation, and we are not making progress. We have already determined that this is not a prompt issue or an API limit issue. The core problem is a systemic, ~50% failure rate of Clay's native LinkedIn scraping function. We are using our own OpenAI API key (GPT-4o Mini), which confirms the failure is happening within Clay's data retrieval step, before our API is even called. This is a critical issue that is cutting our lead volume in half. We need to speak with a person who can look beyond the standard script and investigate a potential technical problem with your platform's infrastructure. Please arrange for us to connect with a live agent

Posted in Clay Support·

John D.

Critical Issue: High Failure Rate in Claygent AI LinkedIn Columns

Hi Clay Support Team, I'm reaching out to report a critical issue we're experiencing with the Claygent AI columns that visit and scrape LinkedIn profiles. For the past weeks, any column designed to visit a person's LinkedIn profile has been failing at an alarmingly high rate—around 50% or more. The columns consistently return an "unable to verify" error. This is specifically affecting crucial parts of our workflow, including: Verify Employment Columns: We use these to confirm a prospect's current role before outreach. Person ICP Columns: Our columns that analyze a person's profile to qualify them are also frequently failing. This issue is having a significant negative impact on our operations. We rely on these features to build qualified lead lists for our clients, and this high failure rate is causing us to lose up to 50% of our potential lead volume. This is a high-priority problem for us. Could you please investigate this immediately and let us know: Is this a known issue with the LinkedIn scrapers? What is causing this high frequency of "unable to verify" errors? What is the estimated timeline for a resolution? Any information you can provide would be greatly appreciated, as our client campaigns are being directly affected.

14Comments

About

Country
My Company Website
Title