This issue looks to be isolated if your rest calls to Airwatch are routing through a MID Server. This release of Service Graph doesn't work when calls are routed through the MID Server. This is due to ServiceNow transitioning to calling the Flow API in a new way.
As a work around until ServiceNow fixes the root issue. Note I've heard many performance complaints after making this change. The job is taking upwards of 18 hours to run.
The fix is to customize the application. Look to the script include called SG_WS1_UEM_Datasource_Helper line 81 in the invokeAction function. Also update line 289 of the loadRemovedSoftwareData() method. Note this script include is read only so you'll have to either make a copy or extend and override these methods.
//change this:
//var result = sn_fd.FlowAPI.getRunner().action(name).inForeground().withInputs(arg).quick().run();
//to this
var result = sn_fd.FlowAPI.getRunner().action(name).inForeground().withInputs(arg).run();
