DevOps Change Velocity cannot connect to the toolIssue <!-- /*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: ; } } When attempting to configure DevOps Change velocity, the following error is received. "com.snc.process_flow.exception.ProcessAutomationException: Role ID doesn't exist: 88a98433d7112100f20bc8170e61033e" 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: ; } } By default, with the out-of-the-box setup, the "oauth_admin" role is included with the package "OAuth 2.0" (com.snc.platform.security.oauth) with the sys_id '88a98433d7112100f20bc8170e61033e'. Navigate to the "sys_user_role" table using the link below and verify its sys_id. If it has a different sys_id in the impacted instance, then the documented error is expected. https://<instancename>.service-now.com/sys_user_role_list.do?sysparm_query=name%3Doauth_admin&sysparm_view= Facts<!-- /*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: ; } } A mismatch in the role sys_id isn't a defect. The sys_id of a role doesn't need to be the same across systems. Roles are coalesced based on their name, not sys_id. Refer to the KB for details. sys_id mismatch for sys_user_role 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: ; } } Supported version of DevOps as available in the ServiceNow app store 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: ; } } The permission check was failing because the backend flow couldn't execute due to a role mismatch with sys_id: 88a98433d7112100f20bc8170e61033e. The following FLOWs failed to execute with the message.["DevOpsCreateTool.createToolOnly","DevOpsOnboardingAPIProcessorSNC.createToolDefault","DevOpsAzureOnboardingAPIHandler","DevOpsToolOnboardingManager.onboardToolFromWorkspace","DevOpsWorkspaceScopeHelper.onboardToolFromWorkspace","Flow action - DevOps Workspace Tool Onboarding","Subflow - DevOps Workspace Tool Onboarding Subflow"] {"SCRIPT_INCLUDE_NAME":"DevOpsCreateTool.createToolOnly","METHOD_NAME":"createToolOnly"} 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: ; } } Option 1 # - Remove the missing role with this hardcoded SysID from the Subflow, such as "DevOps clone oauth credential", and reselect the oauth_admin role in the "Run with roles" list. - Example # https://<instancename>.service-now.com/now/workflow-studio/builder%3Ftable%3Dsys_hub_flow%26sysId%3Db23d572f93c85a10ce900dd548373c4b Note: To find other flows outside the DevOps change velocity module using the default configuration with a hard-coded oauth_admin role sys_id mismatched with the existing one, navigate to sys_hub_flow table, add 'run_as' to the list, and locate records set to run with sys_id '88a98433d7112100f20bc8170e61033e.' Replace it with the current oauth_admin sys_id. Option 2 # - As a workaround, import the oauth_admin role with the sys_id 88a98433d7112100f20bc8170e61033e from the out-of-the-box instance, as attached to this KB. - Before importing the attached role as XML, verify whether a role with sys_id 88a98433d7112100f20bc8170e61033e or the name 'oauth_admin' exists. If it does, take a backup of the associated records with roles such as users, groups, modules, etc., and delete the role manually. ↳https://<instancename>.service-now.com/nav_to.do?uri=sys_user_role.do?sys_id=88a98433d7112100f20bc8170e61033e - After deleting the role, import the role attached to the KB and associate the related records, such as users, groups, modules, etc., - Test the suggestions in this KB in the non-production instance before testing them in the production instance. Also, before deletion, take an XML backup of the role. Related Links<!-- /*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: ; } }