Troubleshooting 500 HTTP Responses from Jamf servers via Service Graph Connector for JamfIssue <!-- /*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: ; } } Customers using the ServiceNow Service Graph Connector for Jamf to import data into ServiceNow may report incomplete imports or import data not coming in at all when running scheduled jobs such as: SG-Jamf Computers - Imports data from computers SG-Jamf Mobile Devices - Imports data from mobile devices In such scenarios, credentials and Roles are setup properly and the errors seen in the Symptoms section below will not be indicative of authentication or authorization issues. Symptoms<!-- /*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: ; } } Overt symptoms include incomplete data imports in the target staging tables used by the integration, data not coming in at all after execution of the scheduled import jobs. Looking at the app node logs you may see messages such as: 2025-02-06 02:00:06 (620) API_INT-thread-3 FE05F7E587AB1A1492CD539D3FBB3569 txid=36053fe569ab FileLogger OUTBOUND_HTTP: protocol=HTTP/1.1 response_status=500 response_time=2146 request_length=0 response_length=45 app_scope=sn _jamf_integrate session _id= transaction_name= transaction_id= user_name=system mid_server=my-mid-host01 source_table=sys_hub_step_instance source_record=37734547537101109f66ddeeff7b1263system_id=app12345.mia123.service-now.com:appnode123 method=GET log_level=All scheme=https hostname={your-on-premise-or-saas-jamf-server} path=/api/v1/computers-inventory Pay attention to the highlighted items above as they may vary slightly in your logs. These messages may also be found in the affected instance's All-> System Logs-> Outbound HTTP Requests module. 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: ; } } All Releases compatible with the Service Graph Connector for Jamf integration Cause<!-- /*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: ; } } Too large a value for Pagination size attributeStale records on the Jamf API server; see https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1703266Corrupt records on the Jamf API server 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: ; } } Scenario 1:Pagination Pagination in the OOB Jamf integration defaults to 1000 records. This may be "too much". You'll want to identify via the logs which specific subflow or action is constructing the REST GET request to pull data from the Jamf API. For example: https://{instance-hostname}.service-now.com/now/workflow-studio/builder%3Ftable%3Dsys_hub_action_type_definition9626sysId%3De1630147537101109f66ddeeff7b129c Click on the "Pagination Setup Step" item in the "Action outline" in the above Workflow Action record link to see the values for the "page-size" attribute. Modifying that attribute/variable value should resolve the HTTP 500 error you are seeing from the Jamf API server. Please change it from 1000 to a smaller value. If you need larger page-size values, you'll need to work with your Jamf admin team to understand their best practices for integrations and what they can support without causing performance issues on the Jamf API server. Scenario 2:Corrupt Jamf records If decreasing Pagination size does not resolve the issue, the customer will need to work closely with their Jamf administrator and have them check the debug logs from the Jamf server. They should check for symptoms related to possible corrupt Jamf records that are being accessed when the SGC for Jamf attempts a REST GET for one of their API endpoints.Using third-party API tools such as Postman or SoapUI or Insomnia or curl will be useful in such troubleshooting to determine if the same HTTP 500 responses are generated by the Jamf API server outside of the ServiceNow instance. Using the instance's Outbound HTTP Requests records that show the 500 error will show you the URL of the REST request that was sent by the instance to the Jamf API server. This can be used to construct a test case using any of the third-party API tools previously listed.