Consolidated Update on Clay Credits, Data Loss, and Support Needs

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
(link: https://app.clay.com/workspaces/491969/workbooks/wb_0sy0k3ofYyk5pVceYcp/tables/t_0sy0k3o27ZSVjbyaEdj/views/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:

1.
Re-credit the ≈ 20 k Clay credits consumed on those failed runs.
2.
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

5 comments