I am trying to disable the Compute Engine API in my project ‘VibeCore’ (PII Removed by Staff)) but I continuously receive the error message: “If Compute Engine API has resources in use, please deactivate them and try again.” The tracking number for the API disablement attempt is: c1868520762652503 I have already taken the following troubleshooting steps: - Stopped and deleted all visible VM instances in the project. - Attempted to delete all persistent disks (the delete button is grayed out). - Uninstalled all Firebase Extensions that were present. - Confirmed the Cloud Workstations API is not enabled/listed for this project. - Confirmed that ‘VibeCore’ (PII Removed by Staff) is *not* part of an organization. - Granted ‘Owner’ and ‘Compute Admin’ roles to my user account (PII Removed by Staff) for this project. - Performed aggressive gcloud CLI cleanup and re-authentication. I need assistance in identifying and removing the specific lingering Compute Engine resource(s) that are preventing the Compute Engine API from being disabled.
Hello @Eric_Roane,
I think that you should take a look at the Cloud Asset Inventory, it could help you find the blocking resource.
Otherwise, you can try to run the gcloud CLI command:
gcloud services disable compute.googleapis.com --force
But note that when using --force:
If specified, the disable call will proceed even if there are enabled services which depend on the service to be disabled or disable the service used in last 30 days or was enabled in recent 3 days. Forcing the call means that the services which depend on the service to be disabled will also be disabled.
Hey,
Hope you’re keeping well.
It’s likely there are hidden or non-VM Compute Engine resources still attached to the project, such as reserved static IPs, instance templates, custom images, snapshots, or regional/zone-specific disks. In Cloud Console, go to Compute Engine > Disks and change the filter to “All locations” to check for regional disks that may not show in the default view. Also check VPC network > External IP addresses for any reserved addresses and Compute Engine > Instance templates or Images for leftovers. You can list all remaining resources via CLI with:
gcloud compute resources list --project PROJECT_ID ``` Once all persistent resources are deleted, the API disablement should succeed from **APIs & Services > Enabled APIs**. Thanks and regards, Taz