Service Graph Connector for JAMF encounters "computersinventory does not exist within application scope: sn_jamf_integrate" error during import "SG-Jamf Computer" - Support and Troubleshooting

Service Graph Connector for JAMF encounters "computersinventory does not exist within application scope: sn_jamf_integrate" error during import "SG-Jamf Computer" Issue .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } We are encountering an error when running the SG-Jamf Computer import schedule: "action does not exist within application scope" error that occurs when running Service Graph Connector (SGC) imports, typically after a plugin upgrade or repair. This error prevents scheduled data imports from completing successfully.

Symptoms .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } A connector import (such as SG-Jamf Computer, SG-Qualys, SG-Tanium, or similar Service Graph Connectors) fails with an error message in the import log or system log Error message format: The action named: [action_name] does not exist within application scope: [plugin_scope] Example: The action named: computersinventory does not exist within application scope: sn_jamf_integrate Error appears in the Import Log or System Log after clicking Run or executing a scheduled import The issue began after upgrading or applying a repair to the connector plugin Imports were functioning correctly prior to the plugin change Facts .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Product area: Service Graph Connectors (SGC) Affected modules: Service Graph Connector (SG-Jamf) Configuration: Custom actions or action-type definitions may exist in the instance Prerequisite condition: Instance contains customized records in the sys_hub_action_type_definition or sys_update_xml tables related to the connector Trigger event: Customized records were skipped during plugin installation, upgrade, or repair due to scope or namespace conflicts Release .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This issue has been observed in multiple ServiceNow releases where Service Graph Connectors are active. Check the plugin version in your instance:

Navigate to Application Manager Search for the connector name (for example, SG-Jamf) Note the version number displayed If you are running a connector version from 2024 or earlier, verify your instance release level and patch status.

Cause .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } During a plugin upgrade or repair operation, the ServiceNow platform skips certain customized records if they are not recognized in the current plugin manifest. When a customized record associated with a connector action (such as computersinventory ) is skipped, the out-of-box action definition is not restored correctly. The connector code then references an action that no longer exists in its scoped namespace, causing the import to fail.

This occurs because:

A custom action-type definition was created in the instance (outside the standard plugin packaging) The plugin upgrade or repair process does not recognize this custom record as part of the standard installation The custom record is marked as skipped in the upgrade history The out-of-box action definition fails to reinstall properly, leaving the connector without a required component Resolution .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Complete the following steps in order. Perform this work during a scheduled maintenance window if possible, as it involves plugin modification and data synchronization.

Step 1: Identify and export the customized record Navigate to System Upgrade History in your instance Search for records related to your connector plugin (for example, filter by sn_jamf_integrate ) Open the upgrade record and note the files marked with Skipped status In a new tab, navigate to the Sys Update XML table ( /sys_update_xml.do ) Locate the customized record matching the skipped action (for example, search for computersinventory or the action name from your error message) Click the Export option or copy the record to your clipboard as a backup Note the system ID of the record you are exporting Step 2: Delete the customized record In the Sys Update XML table, locate the record identified in Step 1 Click on the record to open it Click the Delete button (or use the ... menu and select Delete) Confirm the deletion when prompted Do not delete any other records Important: You are removing only the customized record that is interfering with the plugin. Standard out-of-box records will be reinstalled in the next step.

Step 3: Repair the connector plugin Navigate to Application Manager ( /now/nav/ui/classic/params/target/app_manager.do ) Search for your connector plugin by name (for example, SG-Jamf or SG-Qualys) Open the plugin record Click the Repair button (located in the Quick Actions panel) Click Confirm when prompted Monitor the system logs or wait for a confirmation message (typically 2–5 minutes) Once the repair completes, you should see a success message Note: During repair, the out-of-box action definition (including the one you deleted) will be reinstalled from the plugin package.

Step 4: Validate the fix by testing the import Navigate to Service Graph Connectors > Connectors > [Your Connector Name] (for example, SG-Jamf Computer) Click the Run button or Test button to execute a test import (typically with 20 records) Monitor the import log for completion Verify that no errors appear in the import log or system log Check that records were imported successfully Expected outcome: If the error has been resolved, the import completes without the "action does not exist" error.

Step 5: If the test import succeeds, apply the fix to production (if applicable) If you are testing in a sub-production instance:

Document the exact steps you performed in Steps 1–4 Schedule a change request for your production instance during an approved maintenance window Perform the same four steps in production After completing the production repair, run a production import and confirm successful completion Monitor subsequent scheduled imports to ensure the error does not recur If the error persists after completing these steps Collect the following information: The full error message from the system log (including timestamp and stack trace if available) The connector version and instance release/patch level The exact action name that is not found (from the error message) Export of the Sys Update XML record that was deleted (from Step 1) for reference Contact ServiceNow Support and provide the above information for further investigation Related Links .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 1. Service Graph Connector Product Documentation Latest Release:

Service Graph Connectors - Product Documentation: Yokohama Also available:

Getting started with Service Graph Connectors (Xanadu) 2. How to Roll Back an Application or Plugin Installation in ServiceNow How to roll back an application or plugin installation in ServiceNow 3. Import Set and Transform Map Troubleshooting Guide Primary troubleshooting resource:

Troubleshooting Methods for Import Sets (Master Triage Table with step-by-step guidance) Diagnostic tool:

Import Transform Summary Tool (for troubleshooting import and transform issues) 4. Application Manager Plugin Management Overview Main plugin management resource:

ServiceNow Plugins (overview and core concepts) Alternative resource:

Plugin management guidance Product documentation:

ServiceNow Plugins (official platform documentation)