Addressing Unintentional Credit Overspend from Auto-Update Feature

Hey Clay S. Bo (. LuisArturo — hoping you can help with something we just spotted on our end. Looks like one of our tables has been running on auto-update throughout the month and ended up using a significant number of credits, even though it wasn’t in active use. We hadn’t realized auto-update was enabled or that it would continue running in the background. One of our team members is relatively new to Clay, and this ended up being an accidental (and pretty costly) overspend that we didn’t catch until now. Totally understand if this is expected behavior, but we’d really appreciate your help on two fronts:

1.
How can we make sure auto-updates are fully disabled (either per table or workspace-wide)?
2.
And given the misunderstanding, is there any flexibility to recover some of those credits?

Appreciate you taking a look — happy to follow your guidance on next steps.

6 comments

Bo (.
·
·
Sorry about that—auto-update does need to be turned off manually for each table. There isn’t a workspace-wide setting for it right now. You can follow this guide to review and manage credit usage: http://www.clay.com/university/lesson/clay-credit-conservation Once you’ve had a chance to check with your team, let us know how many credits were used and we’ll see what’s possible.
PJ R.
·
·
Thanks Bo (. - appreciate your willingness to take a look. We pulled the numbers and it turns out that table ended up using 24.7k credits this month (screenshot attached). It was unintentionally left on auto-update and kept running in the background – a tough oversight given the scale. If there’s any way to recover even a portion of those credits, we’d be super grateful. Totally understand if there are limits, but thanks again for being open to working with us on this.
Clay
APP
·
·
Hello PJ! Thanks for reaching out. I talked to the team and got an approval for a refund of the 24.7k credits. They should show up in your account now. I would suggest keeping auto update disabled when working on scheduled tables. I am also attaching this guide that I really recommend to conserve credits and prevent unnecessary usage: https://www.clay.com/university/guide/clay-credit-conservation
Clay
APP
·
·
Going to go ahead and close out this ticket now. Do reach out if you need anything else!
Channeled
APP
·
·
Channeled
APP
·
·
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.

Addressing Unintentional Credit Overspend from Auto-Update Feature | Clay