Hi! I've been facing this glitch in Clay for the last week. Please help. Watch the video here - https://www.tella.tv/video/sayans-video-4y4p
Try a hard refresh to resolve the glitch: Mac: ** Chrome/Firefox: Cmd + Shift + R ** Safari: Cmd + Option + R PC: ** Chrome/Firefox/Edge: Ctrl + F5 If the issue persists, clear your browser cache and refresh the view. For better troubleshooting, please share: ** Summary of what's happening ** Any error messages ** Link to the affected table/workbook * Screenshot if helpful
Can anybody help me out here please?
Hey, This is actually a bug—you shouldn’t be able to change the sources of a column, as that’s not supported right now. I’ve flagged it to our engineering team, and we’ll follow up as soon as there’s an update. The only way to change a source is to create a net new source unfortunately Really sorry about the trouble, and thanks for your patience.
Thanks Bo (., that is really unfortunate, especially considering the subscription cost for your tool.
Can you elaborate: "create a net new source"?
When will it be fixed?
Hey, Totally understand the frustration here. 1. When I say “create a net new source,” I mean you’ll need to delete the current source column and re-add it from scratch with the updated settings. Clay doesn’t currently support changing tables on an existing source once it’s been added. 2. As for timing—we’ve flagged this to the engineering team, but I don’t have a confirmed timeline yet. It’s on their radar, and we’ll follow up as soon as there’s movement. However the fix will prevent you from being able to select another table, not change it. Appreciate your patience, and let me know if you want help rebuilding the source in the meantime.
Thanks and I appreciate you let your product management team know: Bo (. Why Fast Bug Fixing Is Crucial
Retention: Happy users stay—frustrated users churn.
Value Justification: Premium prices require premium reliability.
Efficiency: Users shouldn’t spend hours on workarounds.
Word-of-Mouth: Negative buzz spreads quickly.
Agility: Fast fixes = better product and user loyalty.
Yes, totally agree—the fix is important. That said, it won’t enable the ability to change the source of a column. Right now, it’s not possible to change where a source pulls its data from after it’s been set. Supporting that would require a significant product change, which the team is currently evaluating. Let me know if you have more questions.
First I tried to duplicate the 'Find Jobs' table. But again we faced the same problem - the source is getting defaulted. So instead, I thought of taking another approach. Created a fresh 'Find Jobs' table sourcing the company table (containing 25k companies). In the preview, it showed some relevant jobs posted in the last 3 days. My idea was to just copy the template from the older table and somehow paste the table template in the new 'Find Jobs' table. But the moment I created this new table just to test this approach, the source again defaulted.
Hey, yeah—this is a front-end issue - It’s the same bug we discussed earlier: the front-end shows the wrong source table, even though the back-end is actually using the correct one. Unfortunately, there’s no way to manually change the source of a Find People or Find Jobs table once it’s set. Our team is still investigating this, but I don’t have a timeline for a fix yet. Let me know if you have more questions.
Just a heads up—this issue is showing up in several places, so it definitely needs your urgent attention. It’s a critical part of your software and really shouldn’t be overlooked. Please prioritize fixing this as soon as possible. Thanks! Bo (. @claySupport
Hey ! I also replied to your colleague in their other ticket, but just to be clear: Our team is working on it. The key thing to know is that the bug isn’t blocking a feature — it’s misrepresenting the UI. You are not able to change the source for a Find People Companies or Find Jobs table once it’s been set, and that won’t change after the fix. The issue is that the UI currently shows the wrong source and makes it seem like it’s editable, which isn’t the case. The backend is still using the correct source, so everything continues to run properly — it’s just a display issue. Our team is actively fixing both display issues: showing the correct source and removing the impression that it can be changed. Appreciate your patience while we sort this out. Let me know if you have more questions.
The key thing is that this UI problem means users can’t rely on what they see, which disrupts actual work. In practice, we’ve had to delete and recreate ‘Find People’ tables many times just to avoid errors, which creates confusion, extra effort, and risks mismanaging departments or pulling incorrect data and running incorrect campaings. This isn’t just a cosmetic issue—it’s a core usability problem that makes the software unreliable for everyday use. Please prioritize a fix, or suggest a clear workaround so we can avoid further operational problems. Let us know when this is resolved.
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.
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.