Issues with SG connector for Microsoft Intune - HTTP return status code was 504

[Patilan]

We are using OOTB plugin to import assets from Intune to our SBX env.

The connection test and load is successfull. Test load is successful. Even the data is inserting in the staging tables correctly during the schdule run. But it is not inserting in the target table. 

In the import log I find over 130 k successfull log entries (HTTP response 200), and the following errors

22-11-2023 04:47:09	SG-Intune	Loading import set table cancelled: sn_intune_integrat_devices	ScheduleImportJob
Select record for action: Created 22-11-2023 04:47:09		22-11-2023 04:47:09	SG-Intune	Data was not loaded properly with data source: SG-Intune Devices	ScheduleImportJob
Select record for action: Created 22-11-2023 04:46:59		22-11-2023 04:46:59	SG-Intune	Error executing script : org.mozilla.javascript.JavaScriptException: Error: Unable to make a connection to Intune via Graph API call. Please check your credential configuration. Check system log for more details. HTTP return status code was 504 (sys_script_include.6a4e0342773310102dfb23446810611c.script; line 659)	Loader (SG-Intune Devices)

Despite having 130 k successfull log entries, there are no entries in the target Device table, but only in the staging.

I wonder if it is normal to make so many calls and it seems to me that the Microsoft graph api server cannot handle so many calls.

Has anyone had such issues?

Also, would you reccomend using a MID server?

Thanks

[BhupeshG]

Well in my case i Still received the timeout. All this happens on some of the devices in a specific data center called France central.

[BhupeshG]

my intune has 25 k devices and concurrent batch size is 2k records only.  it gets a time out around after loading 6-8 k devices not sure . i have also noticied the new import set is load only when the the first import set of defined chunk size is loaded.

wondering how concurrent import set is impacting this. Pls advise as if this works, then i need to explain the logic to my customer.

[Patilan]

hi

At the moment there seems to be some issue. Most Imports are canceled automatically. Manual import goes fine. I will have to open a Case to ServiceNow.  There is definetly some issue with the Connector. 
As for the main issue, I managed to fix it by disabling concurrent imports. What's the logic? I don't know.... I had a case with ServiceNow on this, but I really doubt it they have raised a PRB on thjeir side for this. 

[PadmaS]

Hi @Patilan ,

Do you have any info further to this issue? facing the same.

[Jonatan Horvath]

We're having the same issue but the error is not as frequent when you disable concurrent import in the scheduled job.