.png){kind=logo}
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.
