Clay S. just had this error pop up: ErrorFind jobs search failed. Contact Clay support for help (Error code: at_7vmyRoa2enEj). https://app.clay.com/workspaces/443643/workbooks/wb_J9AAnXuBhFj2/tables/t_xfpfZfqzkZSK/views/gv_Tg265KhgXEXe
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.
Is that what you were looking for?
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!
It's happening on all of the scheduled searches
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?
I haven’t checked my other tables LuisArturo I was a bit burnt out from the companies scrapes and just checked that one table
I’ll check the others shortly
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
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
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!
OK mate, going to assume none of our searches will be triggering as a result
Yeah nothing since 21/2 (im in NZ so 23/2 right now)
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.
OK will keep a log
A little disappointing - as this isn't documented anywhere as far as i can see?
No feedback on the import issues just yet. We'll stay tuned as the team comes online and continues investigation. As for the limits, I believe the overall limit is 100 tables with a scheduled source. We have work in flight to make it easier to identify the tables with a recurring schedule, but if you remove/disable a scheduled source elsewhere, it will free up another slot. The scheduling features will have a more formal launch soon – we've been in beta for most of this year.
Ah yeah, it's a beta feature, so some of that is still in the fine-tuning phase, both for error messaging in the UI, assessing where ultimate limits will be for each plan, and so on. I'm sorry this makes things a bit more ambiguous today. We are planning a full set of new documentation when the scheduling features go to general release. Are you currently blocked on anything right now?
Alex, I think you might be all set for now. I'll tentatively mark this closed for the moment, but keep in touch if you hit other roadblocks.
.png){kind=logo}
