Clay is unusable right now. When will the team stop with the automated "help" line, building new features, and actually start to solve the latency and speed issues that have been ongoing for months now? I don't know how much more I can handle here.
We understand your frustration with the performance issues. Large tables and complex workflows can cause latency. To potentially improve speed, try a hard refresh: ** Mac: Command (ā) + Shift + R (Chrome/Firefox) or Option (ā„) + Command (ā) + E (Safari) ** Windows: Ctrl + F5 or Ctrl + Shift + R This often resolves short-term front-end performance issues. If problems persist after trying these steps, please request human assistance by clicking "Talk to a person" for further support.
No it's not helpful. That does exactly nothing to solve my situation
Hi Barnaby, Thank you for reaching out to the support team. I understand your frustration, and Iām really sorry that Clay has been falling short for you lately. I completely understand how difficult it must be to experience latency and speed issues. Behind the scenes, the team has been working hard to address exactly these concerns. Stability and performance are top priorities, and while weāve made meaningful improvements recently, we are constantly working to make things even better, sometimes that means that things don't improve immediately but when we iterate we aim to improve. Your feedback helps reinforce how important this is, and Iāll make sure itās heard. I know that doesnāt immediately solve the experience you're having right now, but please know weāre not ignoring it, weāre actively working to make Clay faster and more stable with every update. Thanks again for your patience and for sticking with us. If thereās any specific action that you're seeing particularly bad performance in, please let us know. If there's anything else we can do in the meantime, let me know.
Hey Barnaby - George here, I head up our support team and just want to double up on what Munnawar said here - is there anything in particular that you find slow/frustrating? We're working on addressing these issues but specific examples are extremely helpful for us.
where do i startā¦
These are my top 3 pains right now;
queries that take forever to complete across all workbooks and has been a problem for the last couple of months - have spoken to other Clay users also with this problem -> I just wish Clay would acknowledge this slowdown is a broader problem rather than constantly asking āwhich workbookā and specify what is being done about it. Itās fine if itās slower because you are making changes to the backend - but tell your customers what the timeline is and manage our expectations
Calculations that just get stuck on āerrorā in workbooks that have previously worked fine. This was a big one yesterday - but also has happened on other days. Clearing cache and reloaded doesnāt help. Basically I have multiple workbooks that just stop workingā¦and then (hopefully) magically start working again a few days later. This isnāt helpful when trying to deliver consistent lead volume daily
The Apify batch import integration seems to have had a lot of issues these past months, as well as the scheduler. Some days they just donāt work at all - again keeping the same sources/actors etc in Apify. The data is being collected in Apify but not being imported clearly and consistently.
Hey Barnaby - appreciate the context here. A few notes from me, but I did DM you as well in case you want to chat more. 1. There unfortunately isn't one systematic thing thats happening (like a backend update) that we can fix to make this better. Part of what we're dealing with is some scaling issues across a number of different things. Layered on with 150+ different integrations, its often pretty difficult for us to point to one reason why things may seem slow which is why we always look for specific details in what you're noticing is slow. Totally understand that the experience can often feel like its across the board, but within that, there are hundred's of things that can be happening. We're of course working on tackling these as quickly as possible, and totally appreciate your patience as we keep at it. 2. I have a hunch on what this may be and I'm happy to provide some more details, but just to confirm - can you clarify what you mean by calculations? Are these specifically formula columns? The best way for us to help here is if we can jump in and see a specific cell that might be "stuck" in an error'd state. If this crops up again, do you mind letting us know so we can jump into it? 3. This is also really helpful detail - do you have examples of specific error messages that you're getting? Specific to #2, if things come up where you're seeing it stuck or broken, the most helpful thing is if we can get in there to see it for ourselves.
.png){kind=logo}
