Scheduled Import doesn't retry in SGC-Intune after cancellation with a 504 response.Issue You are using Service Graph Connector for Microsoft Intune. By default, your Scheduled Imports in Service Graph Connector for Microsoft Intune don't retry in the Imports are cancelled due to a 504 response from Microsoft Intune.CauseThe reason why your ServiceNow instance makes individual requests to each device is to get the "ipAddress" details and "primaryUser" details. The API https://graph.microsoft.com/v1.0/deviceManagement/managedDevices/{{deviceId}}?$select=hardwareInformation is used to get the ipAddress details. The initial API data to pull all the devices and the above API data might almost look similar, but we won't get wiredIPv4Addresses field value in the initial API. Similarly we need to make another API call to get the primary user details. ResolutionFrom version 2.3 of the SGC for Microsoft Intune plugin, there is a possible workaround. If customer is fine with the enrolled user details, then we can skip making this calls. Resolution Steps: 1. Go to Connections from the Filter Navigator: Service Graph Connectors -> Intune ->Connections. 2. Open the connection in which you incurred with this delayed import. 3. Under the Related List, in properties sections you can make "include_primary_user_details" and "include_ip_address_details" as false. Note: However, it comes with a sacrifice. By switching them off (setting to false), your ServiceNow instance won't be pulling the primary user details and also ip address details. It's the choice you have to make to improve the import times. if you can tradeoff ip Address and primary user details for performance, you can modify the properties. This is also mentioned in our documentation (under 'Microsoft Intune connection properties'): https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/configuration-management/task/configure-intune-integration.html