Generic data sources for GCP do not load data into the staging table.Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } We have an out-of-the-box (OOB) implementation of the GCP Service Graph Connector to discover cloud resources in the CMDB. However, we noticed that no data is being imported into the staging table, and the outbound HTTP requests are failing with a 429 error. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Service graph connectors for GCP v 1.9 Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The reason data is not imported using the generic resource data source is that version 1.9 of the SG-GCP connector does not support batch import for generic GCP resources. In this version(v1.9), data is only inserted into the import set table after all records are loaded. If any outbound call fails with a 429 error, all the data is wiped from the staging table — this is expected OOB behavior. Other GCP data sources behave differently: they split resources into batches and invoke a separate flow action for each, allowing partial insertion of resources. Version 1.10 of the SG-GCP connector introduces support for batching with Generic Resources, addressing this limitation. Note: Even after the upgrade, the API Quota limits will still be in effect and '429' errors cannot be avoided, for 429 errors: -if there are multiple accounts available, use a separate one for each instance, as to have a separate quota for each one.-if there is just one account for multiple instances, try to stagger the schedule loading times from the different instances, as each instance calling the API counts towards the same quota limit-if none of the above is possible, consider requesting a higher API quota limit for the project, as there is no way to change the external API behavior from our side Version 1.10 of SG-GCP supports the same for Generic Resources( you can consider to upgrade to this version:https://www.servicenow.com/docs/bundle/store-release-notes/page/release-notes/store/platform-capabilities/store-platcap-rn-service-graph-connector-gcp.html