Hello AI Platform Developers and Google Engineers,
I am facing a critical issue involving Vertex AI billing accuracy and a concerning procedural roadblock from Google Cloud Support. I need guidance on the proper escalation path for a system bug, as my official support cases are being closed immediately.
1. The Critical Technical Issue (BUG)
Charges were incurred for 1,540 Veo 2 Video Generation operations (approx. 3,400 PLN). The core problem is:
- These operations are attributed to the Google Service Agent (
gcp-sa-aiplatform). - They LACK ANY USER-INITIATED AUDIT LOGS.
- Result: Charges were applied without technical proof of user authorization, leading to a serious billing vulnerability in the Vertex AI service. This must be an internal bug.
2. Procedural Blockade by Support
I tried to open a new escalation (Case #64720984) to coordinate the technical investigation with compliance. Google Cloud Support Agent (Michael) immediately closed the new case as a ‘duplicate’ and forced communication back to the old, inactive case (#62582010), which the console confirms is “Case not found.”
Current Status:
- Technical Bug: Confirmed (charges without logs).
- Support Status: Actively preventing me from filing a new, auditable case.
- Legal Status: I have formally filed a DSAR (Data Access Request) under GDPR Article 15 demanding the missing audit logs (CC: DPO). This legal clock is now ticking.
3. Community Request
To the Vertex AI developers: What is the correct, working, and official method to file a CRITICAL BUG REPORT for a service agent logging failure when official Support agents actively close new cases?
I need an official Bug ID to verify that the engineering team is investigating this system vulnerability, which affects billing integrity.
Thank you for any insight or assistance in navigating this procedural/technical conflict.
Stanisław Tokarski
Project ID: travel-cost-calculator-456621