Skip to main content
GCP: Common integration issues/errors

Running into trouble with your Google Cloud Platform integration, this article covers the most common issues and how to fix them

Updated over a year ago

Assets that should be there are missing

You may notice that your GCP assets that should be pulled through (e.g. VMs and Cloud DNS assets) are not appearing in the portal.

Why is this happening?

There are a few reasons for this depending on the method of integration used,

If using OAuth for integration:

  • You may have connected to the wrong Google Account (for example to a personal Google account rather than a work one)

  • You might have enabled an additional API after initial set up (e.g. added Compute Engine API after a time where only Cloud DNS API enabled initially or vice versa)

If syncing individual projects:

  • The Service Account has been created for the wrong GCP Project

  • The Service Account is missing permissions (missing Compute Network Viewer and/or DNS Reader)

  • The Service account was missing permissions initially and the JSON key was exported before the needed permissions were added

How can I fix it?

Not to worry these issues can be generally be addressed by removing and re-adding your GCP integration.

This will temporarily delete all of your GCP targets but don't worry these will be restored as soon as the integration is re-added.


For OAuth:

  1. First up, double check the enabled APIs on your GCP project. To do so head to APIs & Services:

  2. That will open the following dashboard where you can see enabled APIs:

    We're looking for following being listed:

    • Compute Engine API

    • Cloud Resource Manager API

    • Cloud DNS API

  3. That will open the following dashboard where you can see enabled APIs:

    We're looking for following being listed:

    • Compute Engine API

    • Cloud Resource Manager API

    • Cloud DNS API

  4. If any are missing, head to Library from the navigation panel on the left:

  5. Here you can search for each and enable them:

  6. Once done, you can then follow these steps in our GCP integration article to re-add your integration.


For syncing individual GCP projects:

There are a few more things to check here compared to using OAuth, but not to worry, the following steps should help get you sorted!

  1. First up (as above), double check the enabled APIs on your GCP project. To do so head to APIs & Services:

  2. That will open the following dashboard where you can see enabled APIs:

    We're looking for following being listed:

    • Compute Engine API

    • Cloud Resource Manager API

    • Cloud DNS API

  3. If not, head to Library from the navigation panel on the left:

  4. Here you can search for each and enable them:

  5. Beyond this head to the Service Account you created (Welcome page > IAM & Admin > Service Accounts):

  6. Here things do get a bit involved but again not to worry, click on the Service account of interest then head to Permissions and click View Access:

  7. This will then open a pre-filled query builder, where you can click ANALYZE > Run query:

  8. Which will then open this section where you can review the current Roles here:

  9. If any are missing you can head back to the Service Account's Permission here:

  10. Once done, you can then follow these steps in our GCP integration article to re-add your integration.

Did this answer your question?