I need help!

I am a public servant using Project IDX to build an internal administrative dashboard for data visualization (integrated with Google Sheets). I do not have a background in IT, and I am facing a very critical platform behavior regarding automated API key generation. I urgently need this system back online to resume our municipal operations.

Here is the context of what happened:

  1. During a development session, the Project IDX AI assistant/deployment agent apparently entered an infinite loop while trying to establish a connection with the Cloud Run environment to publish the app.

  2. Because of this massive spike in automated requests, the Google Cloud Trust & Safety team flagged and blocked the project for a potential policy violation.

  3. They sent me an email requesting additional information and stated they would take up to 48 hours to review the situation. I have already replied with all the requested details, but the 48-hour period has passed, and I have received no further responses or updates from them.

  4. As a precaution, I have also changed my Google account password and revoked general application permissions to ensure total environment security.

The Current Issue: Even after changing my credentials, revoking permissions, and not triggering any manual actions, the system keeps automatically generating API keys. For instance, today I logged into my Google AI Studio dashboard and noticed yet another new key had been created, even though I did absolutely nothing.

The list has now reached dozens of duplicate keys. It seems that whenever the Project IDX workspace attempts to sync or perform background tasks, it detects the broken permission/connection with the Gemini API and repeatedly attempts to generate a new temporary Generative Language API Key to heal itself. Since the project is locked under safety review, it gets stuck in this endless key-generation loop.

My questions for the community and Google team are:

  • Is this automated creation of multiple API keys a known recovery behavior of Project IDX when a workspace loses its cloud permissions?

  • How can I safely force Project IDX to stop these background key-generation attempts while waiting for a response?

  • Since this is a critical administrative tool for a municipal revenue department and we are facing an urgent deadlock with no reply from the safety team, is there any way to escalate the review process?

I want to emphasize that there is no malicious intent, no external hacker attack, and no commercial use here. It is a strictly internal tool for managing municipal tax exemption decisions. Any guidance on how to stabilize the IDX background sync and get this project unblocked as soon as possible would be greatly appreciated.

Thank you in advance for your help!