Service Graph Connector for AWS is failing to import some resourcesIssue One or more AWS resources are not being ingested into the staging table(s) by the Service Graph Connector for AWS. These instances are visible in the AWS Console and returned by the DescribeInstances API directly, but do not appear in the sn_aws_integ_sg_aws_* staging table.Symptoms- These missing AWS resources may even be within the same AWS account as another resource that is staged.ReleaseNot release specificCauseService Graph Connector for AWS data sources use delta loading to optimize data ingestion. This mechanism compares each resource’s last known update time to the last_run_datetime value stored on the data source record. If the resource has not changed since the last run, it is excluded from the from the import. As a result, previously discovered CIs may not be re-ingested even if deleted from the CMDB, unless the resource metadata has been updated or the delta logic is bypassed by clearing the last_run_datetime field on the affected data sources. This is not immediately obvious because the last_run_datetime field is not displayed on the data source form or list view by default.ResolutionChange the scope to Service Graph Connector for AWSGo to the list view for the affected data source (e.g. SG-AWS-EC2).3. Personalize the columns to include 'Last run datetime'.4. Clear the 'Last run datetime' field.5. Execute the scheduled import for the data source.Related LinksFrom our FAQ: https://www.servicenow.com/community/cmdb-articles/service-graph-connector-for-aws-faq/ta-p/2301015 Q3. I tried to re-import all of the data, but I am not getting it. SG-AWS will update the 'Last run datetime' column after every import schedule. This can be found in the Data Sources table as shown below. If you want to perform a fresh pull, you need to clear the 'Last run datetime' column in all of the rows. The application assumes this as bootstrap load and will pull in all of the data.