Home

Clay Announcements
Clay Support
Discuss Anything
Feedback & Requests
GTM Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

Explore Events
Learn Clay here
Clay Cup

Powered by Tightknit

Frustration Over 2.2k Credits Wasted on Table Errors | Clay

Frustration Over 2.2k Credits Wasted on Table Errors

·

·

I wasted 2.2k credits on this table… Kind of frustrating. Feels like something bugged out as I had conditionals on the write columns but they still sent to a table with a mobile enrich waterfall. https://app.clay.com/workspaces/21913/workbooks/wb_0t4e5b9jRoj8EGhcDTj/tables/t_0t4e6e5XProM7wdfKGt/views/gv_0t4e6e6vDNpYj4XeGWC

3 comments

· Sorted by Oldest

Clay Support
APP
·
·
This sounds like a cross-table enrichment loop issue. When using write to table with conditionals, if the destination table has auto-update enabled, it can trigger enrichments that write back, creating an unintended cycle. [1]
To prevent this:
Add a "processed" flag column to track which rows have been enriched
Use conditional logic like "Only run if [field] is empty" in Run Settings
Turn off auto-update on the destination table while building workflows [2]
To investigate your specific case:
Check if the destination table's auto-update was enabled and whether the write to table action triggered the mobile enrichment waterfall to re-run.
If you need help reviewing your specific table setup, click "Talk to a person" for human assistance.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help resolving the issue with your table and credit usage, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific problems you’re encountering?