Unable to Publish OAuth App or Buy Support. Billing & Support systems are out of sync

Google Cloud Cloud Foundations & Onboarding
1

Hello, I am reporting a persistent platform synchronization bug and am looking for a workaround.

Goal: Publish my ‘Widgetdocker’ OAuth app.

Blocker: The OAuth consent screen shows a ‘Billing account verification’ warning.

Evidence of Bug:

  1. My project (‘Widgetdocker’) is correctly linked to my fully verified ‘Main Billing’ account (ID: [PII Removed by Staff]).

  2. This account has an approved quota of 15 projects.

  3. The project has been linked for over 3 days, but the OAuth warning persists.

This has created a catch-22:

  • Cannot File Support: I am the “Owner” of the project, but I get a permission error when trying to file a technical case (“You don’t have permission to file…”).

  • Cannot Buy Support: I attempted to upgrade to ‘Standard Support’ to fix this, but the ‘Buy now’ buttons are disabled, citing the same billing sync issue.

The core issue is that the OAuth, Support, and IAM services are not seeing the correct, verified status from the Billing service.

Has anyone in the community experienced this synchronization issue or found a way to force a project’s state to be re-synced by an engineer?

5

You’re experiencing a persistent synchronization bug where your verified billing account isn’t recognized on the OAuth consent screen, blocking both support requests and upgrades. Despite linking your project to a fully verified account with sufficient quota, the platform continues showing a billing verification warning, preventing filing cases or purchasing support. This appears to be a backend sync issue between OAuth, Support, and IAM services, and you’re seeking a way to force the project’s state to update or have an engineer manually resync it.