Job Search Error: Contact Support for Assistance Code at_rZKpiQPKEQaR
Hey Team, got this error code when finding jobs: Find jobs search failed. Contact Clay support for help (Error code: at_rZKpiQPKEQaR).
Hey Team, got this error code when finding jobs: Find jobs search failed. Contact Clay support for help (Error code: at_rZKpiQPKEQaR).
I apologize for the inconvenience you're experiencing with the Find Jobs feature. While we don't have specific information about the error code "at_rZKpiQPKEQaR", we can try some general troubleshooting steps: 1. Refresh your browser (use Cmd/Ctrl + Shift + R for a hard refresh). 2. If the issue persists, try running only the affected rows using the error retry option. 3. As an alternative, you can use the find people search feature to locate companies and people while experiencing this issue. If these steps don't resolve the problem, please request human assistance by clicking on "Talk to a person" for further support.
I'm having the same problem 😉
Hey mate, I continued this in my private chat with Clay
They said it's a bug, they're looking more into it
I have a theory of why it could be happening as well, will test it and let you know if I found a workaround
Hey Lazar, merging this with the other bug report. Just a note for next time—one message is enough since they all reach the same place. Thanks!
Hey Daniel, thanks for the note - I continued it in the Clay interface directly because I didn't want to dox my workspace ID 🙂 (and it's linked to a different account than the one that's linked to this slack account)
Having the same issue
Thanks for testing, Lazar. I flagged this with the team. For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change. So what happens now? Now that your issue has been logged, I will tentatively mark this as closed. Please note that I will reach out to you as soon as I receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you.
Im sorry to be so blunt about this but thats not really acceptable. This is like the 5th day this month where Clay has been unusable and the 5th time I have to tell the client that I wont meet the deadline (I provide open jobs daily). At what point do we get compensated?
Hey Lazar, I completely understand your frustration, and I'm really sorry for the disruption this has caused—especially given how it’s impacted your client work. We’re actively working on resolving the issue. If you're using a company filter with a limit, removing that filter may help the query run as expected in the meantime. Again, really sorry you're experiencing this.
Hey, Really sorry this is still ongoing—we’re actively working on it. In the meantime, if your search includes a limit per company filter, try removing that filter. It can help the query run more reliably. Appreciate your patience while we get this fixed.