Clay Search Results Stuck: Help Needed After 18 Hours

Hi! I use the Clay natural language company search and its been 18 hrs and its still stuck in researching and finalising results.

9 comments

Ammar K.
·
·
https://app.clay.com/workspaces/463511/workbooks/wb_0sz36qpmBg8Wx4MGkHx/tables/t_0sz374bcGuTGUSqZcfS/views/gv_0sz374dcDjx3RuHZhwW
Clay
APP
·
·
This delay could be due to API tier limits affecting the processing speed. With lower API tiers, data needs to be processed in smaller batches, which can significantly slow down results. To help troubleshoot this issue, please provide: - A link to the specific table or workbook where this is happening - Any error messages you're seeing - A screenshot if possible If you need further help, you can request human assistance by clicking on "Talk to a person."
Clay
APP
·
·
This delay is likely due to API tier limits affecting processing speed. With lower API tiers, data needs to be processed in smaller batches, which significantly slows down results. Try a hard refresh first: ** Mac: Command + Shift + R (Chrome/Firefox) or Option + Command + E (Safari) ** Windows: Ctrl + F5 or Ctrl + Shift + R If the issue persists, please provide: ** Link to the specific table/workbook ** Any error messages * A screenshot if possible If you need further help, request human assistance by clicking "Talk to a person."
Ammar K.
·
·
I refreshed and its still stuck in processing
Bo (.
·
·
Ammar - Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Ammar K.
·
·
Hey Bo, if you look at the top I’ve shared one.
Bo (.
·
·
Ammar - 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!
Ammar K.
·
·
Perfect thank you
Bo (.
·
·
I’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog. 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. Do you have any further questions before I step away from this conversation until I have an update for you?

Clay Search Results Stuck: Help Needed After 18 Hours | Clay