Howdy, I had a templated table run enrichments prior to a function that was supposed to filter out accounts. It ran through my entire accounts credits when it should have only done 10%
Your templated table likely ran enrichments on all accounts because filtering or conditional logic was not applied before the enrichment step. When enrichments are triggered without pre-qualifying or filtering rows, credits are used for every row, not just a subset like 10% [1].
To prevent this in the future:
Filter or qualify leads before enriching: Set up filters or use conditional runs so only the desired rows (e.g., 10%) are enriched [2].
Use conditional formulas: In the enrichment column’s Run Settings, add a condition (e.g., “Only run if row is in 10% sample”) to limit which rows are processed .
Test on a small batch first: Always run enrichments on a few rows before scaling up to the full table [3] .
Disable auto-update: Turn off auto-update for columns or tables while building or testing to avoid accidental full-table runs .
If you need more help, you can ask to speak to a human.
Is that what you were looking for?
Human
Would you like me to connect you with a human agent? Or if you provide more details about your issue, I can continue to assist you.
Talk to human
I understand, I’m routing you to a human agent now 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 Alton- can you elaborate on the situation? How did it burn through your credits, how were you restricting it to only use 10%? Just want to get more context on these situations.
Hey Alton- are you referring to this formula column. This shouldn't trigger any downstream enrichments. Can you provide me more context here or send a quick video? Thank you!
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!
