John D.

just raised a ticket in the workspace

Hi Bo — yes, this is for the same workspace (cant fully confirm the ID) that was previously shared and where the ticket was submitted. The issue was isolated to a specific AI column failing to retrieve LinkedIn data, which returned errors consistently while comparable columns in the same workspace were running successfully. Let me know if you need anything else to move this forward.

Hey Amit K., thanks for confirming that. Since this issue persisted for about three weeks, and the affected columns were completely non-functional during that time (despite our repeated troubleshooting, tickets, and escalations), we’d like to formally request a partial refund of $525 for the affected period. To clarify: This isn’t a request for Clay credits — we have more than enough. We’re not asking for compensation for API overruns or our clients' lost pipeline. We’re simply requesting a refund that reflects the time during which the platform couldn’t deliver on its core functionality. Let us know what’s needed to get that processed — happy to provide receipts or whatever else is required. Thanks again.

Colin G.

Colin G.

Sayudh M.

https://app.clay.com/workspaces/42993/workbooks/wb_0t6nseoaNvqCxhdUMEA/tables/t_0t6ycmr5owKUsVHr9rz/views/gv_0t5ogpyFtbYhuwGMKBU this is the link for the workbook that doesn't work

But this column for this company doesn't give out one proper result.

As you can see here (the same column/prompt but for different client) its working somehow. these are old data though, I just tested it.

already tried switching to different AI models. Yes its working for other tables