SAM — Miro Enterprise Integration "Connection Validation is Not Successful" Error After Deletion of OOB Connection Alias RecordsIssue <!-- /*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: ; } } Issue When clicking Validate Connection in the SAM workspace for the Miro Enterprise SaaS integration, the following error is returned: Connection validation is not successful. Please check connections and credentials and try again. The system log shows: com.snc.process_flow.exception.OpException: Unable to load connection with alias ID: <sys_id>at com.snc.process_flow.integration.IntegrationDataUtil.retrieveUsingAlias(IntegrationDataUtil.java:62)at com.snc.process_flow.operation.IntegrationConnectionDataResolverOperation.retrieveIntegrationInfoUsingAlias(IntegrationConnectionDataResolverOperation.java:217) The integration may work on one instance but not another, even when using the same OAuth credentials. 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: ; } } No release specific 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: ; } } Cause The SAM SaaS profile defaults table (sam_saas_profile_type_default_value) stores the sys_ids of the out-of-the-box (OOB) Connection Alias records shipped with the Miro Spoke (sn_miro_spoke) for the miro_enterprise_subscription profile type. Specifically, the field download_subscription_connection_credential points to the OOB alias sn_miro_spoke.Miro_Enterprise. If the OOB Connection Alias records (sn_miro_spoke.Miro_Enterprise and sn_miro_spoke.Miro_Enterprise_SCIM) and their associated Connection Attributes are deleted from the instance — for example, as part of a manual reconfiguration — and replaced with new custom records carrying different sys_ids, the IntegrationConnectionDataResolverOperation flow action cannot resolve the alias at runtime. The default value still references the original OOB sys_ids, which no longer exist, causing the validation to fail. The deletion is persisted in sys_update_xml as a retained customization, which prevents the records from being restored automatically on upgrade or repair. 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: ; } } Resolution Restore the four OOB records that were deleted: sys_alias_76b20828c341201021f5e81aa840dded (sn_miro_spoke.Miro_Enterprise)sys_alias_e197e541c345201021f5e81aa840ddd9 (sn_miro_spoke.Miro_Enterprise_SCIM)connection_attributes_23b885bf19772010f877ceeec3a588c6connection_attributes_7b29cdbf19772010f877ceeec3a588ba Step 1 — Clear the deletion customization records Navigate to System Update Sets > Upgrade History > sys_update_xml (or use the URL filter sys_update_xml_list.do).Search for the four record names listed above.For each record, set Replace on upgrade = true. This removes the deletion from the instance's customization log so the upgrade/repair process can restore the OOB records. Step 2 — Remove the custom alias records Navigate to Connection & Credential Aliases (sys_alias.do).Identify and delete any custom Miro alias records that were created as replacements (they will have sys_ids different from the OOB values above). Step 3 — Repair the Miro Spoke Navigate to System Applications > All Available Applications > All.Search for Miro Spoke (sn_miro_spoke).Click Repair (or uninstall and reinstall if Repair is not available for your version). This restores the OOB Connection Alias and Connection Attribute records. Step 4 — Reconfigure and validate Navigate to the restored OOB alias (sn_miro_spoke.Miro_Enterprise) and attach the appropriate Connection & Credential record with valid Miro OAuth credentials.In the SAM workspace, open the Miro Enterprise integration and click Validate Connection.Confirm the error no longer appears.