Hey George & Clay Support Team, Here’s one final, consolidated update with the correct timestamps so we can get this wrapped up quickly. Workspace / Table
Workspace ID: 491 969
Workbook: wb_0sy0k3ofYyk5pVceYcp
Table / View: t_0sy0k3o27ZSVjbyaEdj / gv_0sy0k3pezjm5WDMuAwt
1. Credits & Charges
≈ 20 k Clay credits were burned on 29-30 June while running the “Revenue Pain & Hook” and LinkedIn-messaging columns.
Runs didn’t finish (many rows errored), yet the full cost posted.
I then switched to my own OpenAI API key, but Clay intermittently still deducted Clay credits and/or charged my key. Usage history now shows gaps, so I can’t audit what really happened.
Ask:
Re-credit the ≈ 20 k Clay credits consumed on those failed runs.
Guarantee that any run using my private API key never touches Clay credits.
2. NEW ISSUE – Unwanted Re-Run & Data Loss (Today, 3 July @ ~14:00 BST) At about 14:00 BST I asked support to “reset the table to the state when 1.8 k credits were left.” Instead, the table auto-ran again, using credits (and possibly my API key) and over-writing the custom LinkedIn messages I’d already crafted. The draft messages are now gone and rows are red/errored again. Ask:
Rollback the table to its state from 30 June 12:00 UTC (pre-wipe) or restore the exact cell values in the messaging columns.
Reverse any credits/API spend from today’s unintended run.
3. Subscription Extension Thank you for the 7 k-credit, 14-day trial; however, that can’t cover the lost work. Request: add one full extra month on the Pro plan plus the reinstated credits above so I can finish the campaign without further cost surprises. 4. Live Support Chat delays (24 h+) have already stalled the campaign for three days. Request: a 15-minute call today after 14:00 BST (UTC+1) to walk through:
Credit audit & reinstatement
API-key billing config
Table rollback / data restore
5. Summary of Actions Needed #ActionOwnerDeadline1Re-credit ≈ 20 k Clay credits (or equivalent refund)BillingEOD Today2Extend plan by 1 month (Pro)BillingEOD Today3Confirm API-key runs never consume Clay creditsEngNext Biz Day4Rollback table to 30 Jun 12:00 UTC or restore lost cell values; undo today’s unintended runEngNext Biz Day5Schedule 15-min support call (post-14:00 BST)SupportWithin 4 h I like Clay and want to keep using it, but credit loss and repeated data wipes are blocking an active client campaign. Let’s resolve this today so I can move forward. Please confirm receipt and next steps. Thanks, Joseph
i neeed a human to messsage me
or email me joe@algominds.ai
hello
Hey Joseph - Thanks for passing this over. A few notes 1. We won't charge credits if cells error out, but I've gone ahead and reinstated these credits anyway. If you're using your OpenAI API key, we won't charge credits on those runs so its likely there was something else running in the background. We've run some test on our side to confirm this is the case so we don't think there's a bug here. 2. On your data loss issue, we unfortuantely aren't able to roll-back tables to a previous state, but the 7k credits that we offered yesterday + the credits from today should more than make up for the loss here. One thing to recommend here is to make sure that auto-update (screenshot below) isn't turned on if you're not quite ready to run a table. This will ensure that things don't run unexpectedly. 3. We unfortunately won't be able to extend your pro plan. We're happy to make up for the credits that may have been lost here (as stated above). 4. Totally hear you here - our live support isn't quite live, but its something we're working on making better. Appreciate the feedback you've shared. One other note is that it looks like you're opening up a few different threads for these issues, that can often muddy the waters a bit and make it harder to help you out, so as long as you're still referencing one specific issue, I'd recommend keeping within one app message or slack thread - whichever you prefer. Let us know if you need anything else.

