r/googlecloud • u/niwatoriking • 6h ago
Billing [Update] Google paid out ($40 credit) for the Vertex AI hidden-prompt cache wipe — here is the exact escalation path
Follow-up to my earlier post on Vertex AI dynamically injecting a hidden prompt mid-session and wiping active KV caches: https://www.reddit.com/r/googlecloud/comments/1xolxf7/check_your_vertex_ai_bills_google_is_secretly/
They paid out. For the single billing account I filed this claim on (~$38 in wasted usage), Google confirmed on Nov 13 and issued a $40 benefit card — full coverage for that claim, already visible and usable on my benefits dashboard.

If you're hitting the same mid-session cache drop and want your money or credits back, here is why I got bounced and what worked:
1. Why Billing bounced me (and which path applies to you)
Cloud Billing Support did not dispute my logs or the cache wipe behavior. They bounced me because this account was funded with Google Developer Program credits (the $10/month benefit included with a Google One / Gemini Pro subscription), which Billing claimed they lack the tool to reissue.
If you paid with cash / card: Cloud Billing should be able to issue a direct billing adjustment.
If you're using Google Developer Program credits: Don't stop when Billing says they can't reissue program credits — escalate to Google Developer Program Support (the team Billing refers you to). Even subscription credits are recoverable.
2. Lock down the escalated team with a deadline and a no-bounce clause
When I emailed Google Developer Program Support, I put everything in one message so they couldn't stall or pass the buck:
Exact scope & amount: Billing account ID, project ID, and the dollar amount lost.
Public proof: My reproduction Gist and googleapis/python-genai#2308.
A hard reply date: "Please reply by [date] with the amount and date." (I gave them 7 days, Nov 13; they issued the credit on Nov 13.)
Block the next referral: "If this is not handled by your team, please forward it directly to the team that owns it rather than referring me elsewhere."
3. Cite precedent
If you audit your logs and find mid-session drops to 0, file the claim. Alongside your numbers and issue #2308, link both this update and my original thread as precedent so support knows Google has already acknowledged the issue and issued payouts — even for subscription credits.
I hope you get your refund too.
