Hi 👋 — quick context + help request.
We’re a fund scaling outreach operations with Clay, and we’ve invested significant time/resources building core parts of our workflow on Clay. It’s been working really well overall, and we’re ready to keep scaling our usage — but we’re running into issues that are making it hard to reliably control credit spend.
What’s happening:
We’ve had a couple of instances where credits were consumed unexpectedly because a column auto-ran.
In at least one of those cases, once the run started burning credits, the Stop button didn’t actually stop the action (it appeared to keep running/consuming credits).
What we need help with:
Is there someone we can speak with privately (support/billing) to review what happened and confirm whether any credits can be restored?
Can someone advise on best-practice setup to prevent “full credit spending at once” (safer run patterns, settings to avoid auto-run surprises, etc.)?
Happy to share the workspace/table + column details, timestamps, and anything else helpful. Thanks in advance 🙏
