One of my table ran and consumed a good portion of my credits when I specifically told it not do it. Can I talk to a CSM please?
That's frustrating! This usually happens when auto-update is accidentally left on. Even if you didn't manually run the table, auto-update can trigger enrichments automatically when new rows are added or data changes. [1]
To prevent this going forward:
Click the three dots next to your table name and turn off "Auto-Update Columns"
For individual columns, go to Run Settings and toggle off auto-update
Also check if you might have an infinite loop—this happens when an enrichment updates a field that triggers itself to run again, creating a cycle that burns through credits. [2]
You can see exactly what ran by checking your Table History at the bottom of the table or going to Settings > Credit Usage and entering your table name.
If you need help investigating what happened or want to discuss the credit usage, click "Talk to a person" to connect with our team.
Was that helpful?
I understand your concern and will connect you to a human agent who can assist you further.
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon!
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 Tommy- can you elaborate on what you mean by "telling it not to run."
Hey Amit, happy to elaborate. The tool always tells you about the dependencies and the cost per run. I typically do not proceed with any of these runs if it's > 2k; somehow, this run ate 20k of my credits. I even started auditing all the trigger points per run; this is the first time I have seen this happen. Please let me know what kind of options can be explored to get these credits back. Thank you!
Hey Tommy- just to get more clarity here, you ran the column despite seeing the dependency warnings, and it ate through 20k credits? Could you send me the table link so I could take a closer look. Thanks!
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!
