Cloud Run Deployment Fails Due to Billing Bug in IDX

General
1

Hello IDX Community,

I’m experiencing deployment failures in Google Cloud Run via IDX, despite billing being enabled and correctly linked to my project. The error message suggests an issue reading experiments.yaml, which seems unrelated to billing.

  1. Confirmed Billing is Active

  1. Ensured Correct Project is Selected

  2. Tried Deploying

Deployment failed with the following error:

ERROR: (gcloud.run.deploy) Unable to read the runtimes experiment config:
[gs://gcp-runtime-experiments/experiments.yaml],
error: Could not read [<googlecloudsdk.api_lib.storage.storage_util.ObjectReference object at 0x7ea4aea99250>].
Please retry: HTTPError 403: The billing account for the owning project is disabled in state absent.

Issue Analysis

  • Billing is enabled, but Google Cloud still thinks it’s disabled.
  • The 403 error referencing gs://gcp-runtime-experiments/experiments.yaml suggests a potential issue with Google’s internal configurations rather than an actual billing problem.

Expected Behavior

  • Once billing is enabled and the project is selected, Cloud Run should allow deployments without issues.
  • Since billing is correctly set up, this may be a backend bug in Google Cloud’s IDX integration.

Has anyone else encountered this issue where Cloud Run falsely detects billing as disabled, despite it being enabled? If so, is there a known workaround for IDX users?

Any help would be greatly appreciated! :rocket:

2

Hi @barrymane - thanks for flagging this. We’ll take a look at this on our side.

3

I am facing exactly the same issue . Can anyone look into this. Billing Account is fine.

4

Make sure to triple-check that your project has verified billing. It’s possible to have multiple projects on GCP without any billing associated with them. If you’re using the gcloud CLI, you can check your current project with gcloud config list project. Also, verify your service account permissions in IAM. If your project is already linked, consider removing the link and then re-linking it with the correct billing account. I use Cloud Run all the time.

5

This is happening only from certain IDX project (for me node backend ). I tried a new one it worked, even the existing ones. I am sure its the same project. I think I need to try to move the code to another project and try .

6

It turned out to be challel issue. Updated to channel = “stable-24.05”;
and worked. Newly created worksspaces has buggy channel = “stable-23.11”;

7

We are in the process of updating the Nix channels, I usually use 24.05 too for new projects