Hey — just in case it was missed, I also replied to your Intercom ticket, but wanted to reshare here directly. I’m really sorry all of this is happening — totally understand how frustrating this must be, especially when you’re trying to move fast.
We’ve flagged this as a new bug, and the issue from earlier this week is also still being tracked. I’ll keep you posted as soon as I hear anything from engineering.
In the meantime, to help get you unblocked, I added 10,000 Clay credits to your account and tested a run using those — everything worked fine, which makes it likely this is related to your API key setup.
You’re welcome to use those 10,000 credits to run things without hitting issues while we sort this out. And if you’re not seeing my reply in Intercom, let me know and I’ll resend it.
Also sharing again here in case it helps troubleshoot:
Also, Ty — sorry, I see a lot of threads, so I’ll answer here since this is where we’ve linked the previous bugs. I just tested in your account using Clay credits, and everything seems to be working on our end, which points to an API key issue (unrelated to the previous bug). I’ve still raised it as a new bug and will wait for our engineers to confirm.
To help narrow it down, could you confirm a couple things:
What type of API key are you using, and what tier is it on?
Is the key set up to handle the volume of requests you’re sending?
Could rate limits be affecting performance based on your current setup?
Let me know and we’ll dig in further from there.
.png){kind=logo}
