My Google Cloud project was recently suspended for alleged repeated Terms of Service violations. I already submitted an appeal, but the appeal page does not show the original appeal, its status, history, or any way to add more information.
After submitting it, I realized what I think was the likely trigger.
Right before the suspension, I ran a one-time automated Gemini/Vertex batch job that analyzed and categorized hundreds of short video clips for a legitimate commercial media library. It involved roughly 693 source assets and 1,076 reusable clips.
The workload was intentional, but it may have created an unusually large burst of multimodal requests. There was no spam, scraping of Google services, malware, credential abuse, DDoS activity, quota circumvention, or compromised account.
The suspension email also mentioned that a warning may not be sent when project behavior is seriously impacting other users, which makes me think this batch job may have triggered an automated abuse system.
I am happy to reduce concurrency, split future jobs into smaller batches, add more aggressive backoff, and provide logs or technical details if needed.
Is there any supported way to add this information to an appeal that is already pending, or otherwise get this additional context in front of the review team?
