Veracode tool connection fails with "Tool can't be connected due to a technical issue" in DevOps Change VelocityIssue <!-- /*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 you attempt to connect Veracode to the DevOps Change Velocity module via DevOps Tool Connect, the connection fails even after the required roles have been assigned. 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: ; } } - The tool connection fails with the on-screen message: 'Tool can't be connected due to a technical issue.'- The DevOps error log records a script action error: 'No Response received from sn_vul.VulnerabilityResponseDevOpsIntegration().validateIntegrationConnection'- The security integration log records: 'Implementation not configured: <implementation-sys-id>' as mentioned below- Both the Test Connection button on the tool and the Resume Tool Connection playbook fail with the same error.- The failure persists after the user logs out and back in and restarts onboarding from the beginning.- The failure persists even after the 'sn_vul.app_sec_manager' , 'sn_vul_veracode.configure_integration' ,'sn_devops.admin' or 'sn_devops.tool_owner' roles are granted 2026-08-03 11:41:41 (177) Default-thread-16 6D9386A0936AC3D0948EFE5FA903D67A txid=11b34ea0936a RhinoExceptions SEVERE *** ERROR *** Root cause of JavaScriptException: org.mozilla.javascript.ConsString JavaScript evaluation error on: (function validation(configId) { var valid = false; try { var response = new sn_vul_veracode.VeracodeUtil().getApplicationListForValidation(configId); valid = response.getStatusCode() == 200; var impl = new GlideRecord('sn_sec_int_impl'); if (impl.get(configId)) { impl.setValue('validation_status', valid ? 'valid' : 'invalid'); impl.update(); } return response; } catch (error) { gs.error(error); throw error; } })(sn_sec_int_impl); Stack trace: at sn_sec_int_integration.ffefc949773d4010250396e66910617f.validation_script:16 (validation) at sn_sec_int_integration.ffefc949773d4010250396e66910617f.validation_script:18 at sys_script_include.93d4b8ad53aa2110faccddeeff7b12cb.script:52 at sys_script_include.93d4b8ad53aa2110faccddeeff7b12cb.script:9 2026-08-03 11:41:41 (176) Default-thread-16 6D9386A0936AC3D0948EFE5FA903D67A txid=11b34ea0936a sn_vul_veracode SEVERE *** ERROR *** sn_vul_veracode: Implementation not configured: 6a78e4e82bea4f9061d6f527ce91bffe 2026-08-03 11:41:41 (118) Default-thread-16 6D9386A0936AC3D0948EFE5FA903D67A txid=11b34ea0936a SSI_93d4b8ad53aa2110faccddeeff7b12cb sn_vul (VulnerabilityResponseDevOpsIntegration): Validating connection for implementation: 6a78e4e82bea4f9061d6f527ce91bffe 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 currently supported 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 fails because the API ID and API key entered in the Connect Tool wizard are not correctly written to the Veracode implementation configuration's connection parameters. 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: ; } } Navigate to the Veracode tool record (sn_sec_int_impl) you created under DevOps Tool Connect2. Open the associated security integration implementation configuration for the tool.3. Locate the connection parameters that hold the API ID and API key as shown below.4. Manually enter the correct API ID and API key values into these parameters and save the record. NOTE - The values must match the credentials generated in your Veracode account for API access.5. Return to the tool and click Test Connection, or run the **Resume Tool Connection** playbook.6. Confirm the validation completes, and the tool moves to a connected state. Note: If you need to recreate the tool, be aware that deleting a tool does not always remove related records. A running process flow context and residual records in the vulnerability application can remain and prevent you from reusing the same tool name. Confirm that those records are cleaned up before recreating a tool with an existing name. 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: ; } } Onboard Veracode to DevOps Change Velocity - Workspace