Urgent: LinkedIn Access Failures and API Credit Loss Investigation Needed
: 🚨 Urgent Issue: Repeated LinkedIn Access Failures + Excessive API Credit Loss 🚨 Hi Clay team we need immediate help with a blocking issue that’s costing us significant API usage and credits. For one specific client, a column consistently returns errors like “Unable to access LinkedIn info” / “Could not access LinkedIn”, despite the exact same column setup working correctly for our other clients. To rule out configuration issues on our end, we’ve already exhausted all standard and advanced troubleshooting steps:
- 1.
Duplicated the problematic column and tested it in other tables
- 2.
Created a brand-new AI column from scratch to see if it works
- 3.
When #2 worked, rebuilt the Agentiiv AI column entirely from scratch
- 4.
Duplicated the entire table (with the same data) and reran everything
➡️ None of the above resolved the issue. ➡️ The error persists only for this client. ➡️ Each attempt is consuming real API calls / credits, and the cost is adding up fast. We have strong internal SOPs and are confident this is not a user-side configuration issue. At this point, continued retries are not viable — this is burning credits due to what appears to be a Clay-side bug or LinkedIn access inconsistency. We need:
Immediate investigation from the Clay team
Clarity on why this client’s data behaves differently
A refund for the API calls / credits consumed during troubleshooting, as this was unavoidable and outside our control
Happy to share table URLs, column IDs, logs, or anything else needed — but we need this escalated ASAP.
