DevOps Change Velocity for GitHub: "Auto Configure with Existing Token" Fails with no visible action or result occurringIssue <!-- /*NS Branding Styles*/ --> .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: ; } } When clicking "Auto configure with existing token" on a GitHub Repository record in Change Velocity, the operation fails immediately with no visible indicator that the action was successful or failed. Checking DevOps Error log you may see items such as: existing webhooks cannot be retrieved.Request not sent to uri Symptoms<!-- /*NS Branding Styles*/ --> .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: ; } } Node logs display the error: Request not sent to uri= __SECURITY_CONSTRAINT__/repos/<REPO_NAME>/itsa-actions-test/hooks : java.lang.IllegalArgumentException: host parameter is nullDevOps Error log displays the secondary error: Existing webhooks cannot be retrieved.MID Server / node logs contain an outbound HTTP entry with response_status=-1, scheme= (blank), and hostname= (blank), indicating the connection record's host could not be resolved:2026-03-06 12:03:54 (942) Default-thread-43 F7D53558472BF618326803DC426D43D5 txid=ab08bd98472b FileLogger OUTBOUND_HTTP: protocol=HTTP/1.1 response_status=-1 response_time=0 request_length=0 response_length=-1 app_scope=sn_devops session_id=F7D53558472BF61832680 3DC426D43D5 transaction_name="#805825 /api/now/ui/ui_action/6750f392538301104a6eddeeff7b123e" transaction_id=ab08bd98472bf618326803 dc426d4370 user_name=XXX mid_server= source_table=sys_script_include source_record=cf1a9a90675223008b52f3b457415ac5 system_id=appXXX.hefXXX.service-now.com:xxxx15025 method=GET log_level=All scheme= hostname= path=__SECUIRTY_CONSTRAINT__/repos/XXX/itsa-actions-test/hooks Facts<!-- /*NS Branding Styles*/ --> .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: ; } } Feature: Change Velocity — GitHub integration, webhook auto-configurationTable involved: sys_connection (Connections & Credentials)ACL in question: Name sys_connection.*, Operation readThe outbound HTTP call is executed within the sn_devops app scope Release<!-- /*NS Branding Styles*/ --> .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: ; } } All Releases Cause<!-- /*NS Branding Styles*/ --> .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: ; } } The connection record host resolves to blank/null because the executing user lacks read access to the sys_connection recordRoles currently present on the ACL: connection_admin, mid_serverRole missing from ACL: sn_devops.tool_ownerThe "Auto configure with existing token" action in Change Velocity reads the associated Connection record (sys_connection) to retrieve the GitHub host URL. The ACL controlling read access to sys_connection.* does not include the sn_devops.tool_owner role in its Required Roles conditions. As a result, users with the Tool Owner role cannot read the Connection record, the hostname is returned as null, and the outbound webhook API call fails with a java.lang.IllegalArgumentException: host parameter is null error before it is dispatched. Resolution<!-- /*NS Branding Styles*/ --> .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: ; } } Add the sn_devops.tool_owner role to the Required Roles section of the sys_connection.* read ACL. Navigate to All and search for Connections.Under the Connections & Credentials section, select Connections to open the Connections list.Right-click any column header and select Configure → Table to open the table configuration record.Scroll to the Related Links section and click Access Controls.Locate the ACL record with Name: sys_connection.* and Operation: read, then open it. Alternatively open the ACL directly: .../nav_to.do?uri=sys_security_acl.do?sys_id=c451f70db3323200350086d256a8dcf3 Scroll to the Conditions section and find the Required Roles related list.Click Insert a new row and enter sn_devops.tool_owner.Save the ACL record.Re-attempt the "Auto configure with existing token" action on the GitHub Repository record in Change Velocity to confirm the issue is resolved.IMPORTANT NOTE: Some customers may make the following observation after the fix: The tool owner role gives too much access to developers who only need to view or configure their pipeline. Is there a way to limit this so developers can see only the pipelines that they are responsible for maintaining by group?Response: Please referto the ServiceNow product documentation for possible options regarding the included out-of-box Roles and their permissions. See the link below and Step 4 and 5 of the Procedure section:https://www.servicenow.com/docs/r/it-service-management/devops-change-velocity/create-github-tool-dev-ops.html ########## It you want to control access to the tool, add the groups that must be given access to the tool in the Maintained by field on the Access tab. The tasks the users in the groups can perform depends on the roles assigned to them. DevOps Tool Owner role: Can view and edit the tool. DevOps App Owner role: Can view the tool and can associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects (such as plans, repositories, and pipelines). DevOps Administrator role: Can edit all tools. Other Devops roles: Can view the tool. Note: Only groups containing users with DevOps roles are available for selection in the Maintained by field. The All App Owners can view and associate tool objects to applications option becomes available for selection if you choose to restrict access to the tool. This option enables all users having the Devops App Owner role to access the tool If selected, they'll be able to view, associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects. ########## You might be able to modify the Roles of the user in question to try and limit/restrict their access. Recommend you test this in subprod if you want to experiment with the Roles assigned to the affected user. Otherwise, if you cannot restrict the access per your preference; you should consider reaching out to your SAM to begin a Professional Services Consultation with ServiceNow to explore that topic in-depth with you. Related Links<!-- /*NS Branding Styles*/ --> .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: ; } } https://www.servicenow.com/docs/r/it-service-management/devops-change-velocity/create-github-tool-dev-ops.html