I'm using Pulumi to deploy a Cloud Run services for preview builds. This generally works great until someone open a PR with a container that doesn't start up:

gcp:cloudrunv2:Service (backend):
      error:   sdk-v2/provider2.go:520: sdk.helper_schema: Error waiting to create Service: Error waiting for Creating Service: Error code 13, message: Revision 'backend-gh-69-00001-pmg' is not ready and cannot serve traffic. The user-provided container failed the configured startup probe checks. Logs for this revision might contain more information.

The resource failed to be created -- but the the service was still created on Google's side. That means that once the bug is fixed, subsequent deployments fail like:

gcp:cloudrunv2:Service (backend):
      error: 1 error occurred:
      	* Error creating Service: googleapi: Error 409: Resource 'backend-gh-69' already exists.

Any ideas for a workaround?

Sorry I don't have any workarounds for you but I pointed out to Pulumi reps we are working with that it was very frustrating using Pulumi with gke as I've seen often similar situations there as well. IMHO Pulumi should check if the resource is there and if it is clean it up but I think that's a big change to how the gcp provider does things