Clay Jobs Search Error: Contact Support for Immediate Assistance

Alex J. · 2025-02-22T01:19:04.029Z

just had this error pop up: ErrorFind jobs search failed. Contact Clay support for help (Error code: at_7vmyRoa2enEj).

Clay Jobs Search Error: Contact Support for Immediate Assistance | Clay

Channeled
APP
·
·
To resolve the "ErrorFind jobs search failed" issue, try these steps: 1. Clear your browser cache and refresh the page. 2. If the error persists, try adjusting your search parameters: • Review and broaden your job title keywords • Adjust the per-company limit settings • Include various permutations of job titles 3. If these steps don't work, you may need further assistance. Click on "Talk to a person" in the chat to request human support for this specific error code.
Source: Find Jobs Source + Enrichment [Clay 101] - Clay University
Channeled
APP
·
·
Is that what you were looking for?
Channeled
APP
·
·
Looks like you're still looking for help.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Alex J.
·
·
It's happening on all of the scheduled searches
LuisArturo
·
·
Hey there Alex thanks for reaching out, question do you happen to have any other tables where this is occurring so that we can take a look as well?
Alex J.
·
·
I haven’t checked my other tables LuisArturo I was a bit burnt out from the companies scrapes and just checked that one table
Alex J.
·
·
I’ll check the others shortly
Alex J.
·
·
I also got a notification that we have maxed out our number of automated sources with the last company search I did - so had to delete it
Alex J.
·
·
Happening in this table too LuisArturo Click sources on first column > choose any source > error code. https://app.clay.com/workspaces/443643/workbooks/wb_E4YARiKwDUZX/tables/t_UJtCUUihCP3k/views/gv_Tx2nJpyEQfK2
Bo (.
·
·
Hey Alex - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Alex J.
·
·
OK mate, going to assume none of our searches will be triggering as a result
Alex J.
·
·
Yeah nothing since 21/2 (im in NZ so 23/2 right now)
Bo (.
·
·
Those errors typically come from timeout issues or lack of data - not necessarily a systemic problem. Since we're not seeing widespread reports, your searches might still be working as normal. Either way it's always better to wait from our engineers till we know more.
Alex J.
·
·
OK will keep a log
Alex J.
·
·
Any updates from the engineers Bo (.?

21 comments