If i'm out of clay credits - can i not use any of the native search functions? Company / people / job search. It's letting me do a company search - then displays results for a few seconds and then sends me to an error screen. We've burnt through 10K credits rebuilding our clay environment lol. Clay S.
List building and prospecting features, including the native search functions for companies, people, and jobs, are free to use in Clay and don't consume credits.However, if you're seeing results briefly before getting an error screen, this might be related to attempting data enrichment after finding the results. Data enrichment actions (like getting additional information about leads or accounts) do require credits since Clay needs to pay data providers for this information.When using Find People Search, you can: 1. Define your search parameters 2. Set result limits 3. Preview the results 4. Import them into your tableTo avoid unexpected credit usage, be mindful of any auto-update settings in your tables that might trigger automatic enrichment of the data. Sources: Find People overview | Documentation | Clay University FAQ | Clay.com
There's no enrichment happening as im not importing results into Clay - yet. Im simply running the preview - to see the number of results.
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!
Hey there Alex thanks for reaching out, sorry for the delay, this error was occurring due to a bug that Clay was experiencing. It has since been fixed, so you should be able to search for companies.
Still experiencing the same thing LuisArturo
Ah I see can you send me a screenshot of the filters you are entering so that I can take a look at this
It only seems to happen when the search returns >25K results and i hover the search results number to try and see total number of results from the search.
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!
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.