Issue with Claygent Column Causing Unintended Reruns and Costs

Hey team, just wanted to point out that I clicked the play button on a Claygent column > then "Run all rows that haven't run or have had an error" and it reran my entire column. Was dissapointing because it likely cost me $50+ in API costs as well as several Clay credits. Our team is running on a tight budget so bugs like this on 600+ rows can be pretty devastating. Now I'm getting several errors due to rate liimts, and am afraid that clicking it again will just run the entire column again. Clay team: is there any way that you could restore the state that the table was in around an hour ago (7:00 PT)? (EDIT: Nevermind, please do not restore the table) And please let me know when you've found a solution to this bug. Thank you

6 comments

Clay
APP
·
·
Unfortunately, we don't have a built-in feature to restore tables to previous states or create automatic backups of table data. The "Run all rows that haven't run or have had an error" option is designed to process rows that either haven't been processed or encountered errors, but if it reran your entire column unexpectedly, this suggests there may have been an issue with how the system detected the row states. For the rate limit errors you're experiencing, you'll need to wait for the API limits to reset before running the column again. To avoid rerunning the entire column, you could try filtering for only the rows that actually need to be processed and then running the enrichment on that filtered view. What specific type of enrichment or integration were you running in this Claygent column when the issue occurred?
Source: Run Options
Dustin S.
·
·
https://app.clay.com/workspaces/590277/workbooks/wb_0svwz70wSARsNR8YtgX/tables/t_0svwz70PoKnuoNbUdgG/views/gv_0svwz71R5dDEYS2bqxd
Dustin S.
·
·
Hey all, I just want to make it abundantly clear - I am 100% confident I clicked the option to only re-run rows that did not run or had errors. This is a very disappointing bug.
Bo (.
·
·
Hey, really sorry about that — I get how frustrating this must be. Just to clarify, this isn’t a bug. When you make any change to an AI column (even saving it again), it creates a new state. That means when you choose “run rows that haven’t run or had errors,” it sees all rows as new and reruns them. That said, since it’s your first time running into this and it caused unexpected costs, I’m happy to add few credits back. Just let me know how many you’d like restored.
Dustin S.
·
·
Hey Bo, I understand and appreciate the clarification. Thanks for the offer as well. If you could possibly restore ~1500 credits, that would be greatly appreciated.
Bo (.
·
·
Done ✅ Let me know if you have more questions

Issue with Claygent Column Causing Unintended Reruns and Costs | Clay