Cloud Discovery Fails Post Clone<!-- /*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: ; } } *, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; } :root { --infinite-blue: #032D42; --wasabi-green: #63DF4E; --bright-blue: #52B8FF; --bright-indigo: #7661FF; --bright-purple: #BF71F2; --accent: var(--wasabi-green); --accent-light: #e8fce4; --border: #d0dbe0; --text-primary: #0d1f2b; --text-secondary: #3d5a6a; --bg-card: #ffffff; --warn-bg: #fff4e0; --warn-border: #e6a817; --note-bg: #e6f4ff; --note-border: var(--bright-blue); --tag-bg: #e8fce4; --tag-color: #032D42; --radius: 6px; } body { font-family: 'Lato', sans-serif; font-size: 15px; line-height: 1.7; color: var(--text-primary); padding: 0; margin: 0; } .kb-wrapper { max-width: 100%; } /* ── Plain title ── */ .kb-title { font-size: 18px; font-weight: 900; color: var(--infinite-blue); margin-bottom: 20px; } /* ── Body ── */ .kb-body { padding: 0; } /* ── Sections ── */ .section { margin-bottom: 34px; } .section:last-child { margin-bottom: 0; } h2.section-title { font-size: 16px; font-weight: 900; color: var(--infinite-blue); margin-bottom: 14px; padding-bottom: 8px; border-bottom: 2px solid var(--accent-light); } /* ── Text ── */ p { margin-bottom: 12px; color: var(--text-primary); } p:last-child { margin-bottom: 0; } ul, ol { padding-left: 22px; margin-bottom: 12px; } li { margin-bottom: 6px; } li:last-child { margin-bottom: 0; } /* ── Inline code ── */ code { font-family: 'Courier New', Courier, monospace; font-size: 13px; background: #e6f0f5; color: #032D42; padding: 1px 6px; border-radius: 3px; border: 1px solid #b8cfd8; } /* ── Callouts ── */ .callout { border-left: 4px solid var(--note-border); background: var(--note-bg); border-radius: 0 var(--radius) var(--radius) 0; padding: 13px 16px; margin: 16px 0; font-size: 14px; } .callout.warn { border-left-color: var(--warn-border); background: var(--warn-bg); } .callout strong { display: block; margin-bottom: 4px; font-weight: 700; } /* ── Ordered steps ── */ .steps-list { list-style: none; padding-left: 0; counter-reset: steps; } .steps-list li { counter-increment: steps; display: flex; gap: 14px; align-items: flex-start; margin-bottom: 14px; } .steps-list li::before { content: counter(steps); flex-shrink: 0; width: 26px; height: 26px; background: var(--infinite-blue); color: var(--wasabi-green); border-radius: 50%; font-size: 12px; font-weight: 900; display: flex; align-items: center; justify-content: center; margin-top: 2px; } /* ── Related links ── */ .related-list { list-style: none; padding-left: 0; display: flex; flex-direction: column; gap: 8px; } .related-list li { background: var(--tag-bg); border: 1px solid #a8dfa0; border-radius: var(--radius); padding: 10px 14px; margin-bottom: 0; } .related-list li a { color: var(--infinite-blue); text-decoration: none; font-size: 13.5px; font-weight: 700; } .related-list li a:hover { text-decoration: underline; color: #0057a8; } /* ── Footer ── */ .kb-footer { margin-top: 20px; font-size: 12px; color: #6a8a9a; text-align: center; line-height: 1.6; } hr.section-divider { border: none; border-top: 1px solid var(--border); margin: 30px 0; } Issue / Question Cloud Discovery fails on a target instance following a clone from a source instance. The Discovery Credentials field on the Service Account contains a Sys ID or null value with no Display Name, and no matching record can be found on the Discovery Credentials table. Symptoms The Cloud Discovery Schedule runs successfully on the source instance prior to the clone.The same Cloud Discovery Schedule fails on the target instance after the clone.The Discovery Credentials field on the Service Account displays a Sys ID or null value instead of a Display Name.No record is found on the Discovery Credentials table matching the Sys ID stored on the Service Account.Discovery Pattern Logs contain an error stating that credentials could not be found. Facts The Discovery Credential record exists on both the source and target instances, but each instance holds a different Sys ID for that record.Following the clone, the Service Account retains the Sys ID of the credential from the source instance.The target instance cannot resolve the credential because the stored Sys ID does not match any record on the target instance's Discovery Credentials table. Cause During a clone, the Service Account is overwritten with data from the source instance, including the Sys ID of the Discovery Credential as it exists on the source. Because the same credential record on the target instance has a different Sys ID, the reference becomes broken — the Service Account points to a Sys ID that does not exist in the target instance's Discovery Credentials table. Important This is a known post-clone configuration issue. Discovery Credential references must be revalidated on the target instance after any clone operation that overwrites Service Account records. Solution Update the Discovery Credentials field on the Service Account to reference the correct credential record on the target instance. Navigate to the affected Service Account on the target instance. Go to Discovery > Cloud Service Accounts and open the Service Account used by the failing Cloud Discovery Schedule. Identify the broken credential reference. Confirm that the Discovery Credentials field shows a raw Sys ID, null, or missing Display Name — indicating the reference is pointing to a non-existent record. Locate the correct credential on the target instance. Navigate to Discovery > Credentials and find the credential record that corresponds to the one used on the source instance. Update the Discovery Credentials field. On the Service Account, clear the current value in the Discovery Credentials field and re-select the correct credential from the target instance. Save the record. Re-run the Cloud Discovery Schedule and validate. Trigger the Discovery Schedule manually and confirm it completes successfully. Verify that credentials are resolved correctly in the Discovery Pattern Logs with no credential errors. Post-Clone Best Practice After any clone operation, review all Cloud Service Accounts on the target instance and verify that Discovery Credential references resolve correctly before running Discovery Schedules.