Subject: Cannot publish/deploy from AI Studio — "service is unavailable" for 48+ hours (existing revision healthy)

Google AI Studio
1

Hi,

I’m unable to publish new versions of my app from Google AI Studio. Every attempt fails with:

“Failed to update Cloud Run service: service is unavailable. Please try again later.”

This has now persisted for more than 48 hours, across many retries, page refreshes, and different browsers.

Project / service details:

  • AI Studio app deployed to Cloud Run
  • Google Cloud project: prime-oficial (project number 120536705..)
  • Cloud Run service name: prime-oficial
  • Region: us-west2
  • Firestore database in use: (default) (production), with a secondary AI Studio-managed database ai-studio-7b93c818-c189-4fca-8df7-371f9551…
  • Deployment origin: AI Studio (managed-by: google-ai-studio)

What I’ve already checked / ruled out:

  • The currently published revision (prime-oficial-00102-2nl) is healthy and serving 100% of traffic — the live app works fine.
  • No new/failed revision is being created in Cloud Run when I hit Publish. It seems the deploy fails before a new revision (00103+) is ever generated.
  • Cloud Run logs show no container startup errors, no OOM, no port errors, no Secret Manager/permission errors, and no quota-exceeded messages. Startup TCP probes succeed on port 3000.
  • The error string “service is unavailable” / “Failed to update service” does not appear in the Cloud Run logs — suggesting the failure happens at the AI Studio / control-plane layer, not in my container.
  • The Google Cloud Status Dashboard shows Cloud Run as operational, with no active incident for my region.
  • All required environment variables are populated in the app’s settings.

My conclusion: the issue appears to be in the AI Studio publish pipeline for my specific project, not in my application code or Cloud Run configuration (the container builds and runs correctly, as proven by the healthy live revision).

Questions:

  1. Can you check whether there’s a stuck or failed deployment/build job for the prime-oficial service that needs to be cleared on your side?
  2. Is there anything specific to my project blocking the Publish flow from creating a new revision?
  3. If the AI Studio publish pipeline can’t be restored quickly, can you confirm the recommended workaround (e.g., deploying a new revision directly via gcloud, which is how revision 00102 was previously deployed)?

Thank you very much for your help.