Cloud Discovery schedule stuck in starting stateIssue <!-- /*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: ; } } .kb-wrapper-2976976-iss { font-family: Lato, sans-serif; max-width: 100%; line-height: 1.7; } .kb-wrapper-2976976-iss p { font-size: 12pt; color: #000; margin: 0 0 12px 0; } .kb-wrapper-2976976-iss .error-msg { font-style: italic; margin: 12px 0 12px 20px; } .kb-wrapper-2976976-iss .callout-note { border-left: 4px solid #52B8FF; background: #e6f4ff; padding: 10px 14px; margin: 12px 0 0 0; font-size: 12pt; } .kb-wrapper-2976976-iss .callout-note strong { color: #032D42; } Resolve Cloud Discovery schedules that remain stuck in the starting state and eventually cancel when the maximum runtime is exceeded. When you run the schedule manually using the Discover Now action, the Discovery Status record is not created and the following error appears: "No active range or web service or necessary parameters specified for Discovery" Note: This error only appears when you run the affected schedule using the Discover Now action. Scheduled executions do not display this error. 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: ; } } .kb-wrapper-2976976-rel { font-family: Lato, sans-serif; max-width: 100%; line-height: 1.7; } .kb-wrapper-2976976-rel p { font-size: 12pt; color: #000; margin: 0; } Any 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: ; } } .kb-wrapper-2976976-cau { font-family: Lato, sans-serif; max-width: 100%; line-height: 1.7; } .kb-wrapper-2976976-cau p { font-size: 12pt; color: #000; margin: 0 0 12px 0; } .kb-wrapper-2976976-cau ul { font-size: 12pt; margin: 0 0 12px 0; padding-left: 20px; } .kb-wrapper-2976976-cau li { margin-bottom: 6px; } .kb-wrapper-2976976-cau code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 5px; border-radius: 3px; font-family: monospace; font-size: 10.5pt; } This issue occurs when the Discovery schedule cannot find the required configuration records for the Cloud Discovery schedule. The Discovery schedule looks up related records using the sys_id of the [discovery_schedule] record as the reference key. Two tables must contain records that reference the schedule: [discovery_schedule_extend_params] — stores the provider type (for example, AWS or Azure) for the schedule[cmp_discovery_ldc_config] — determines which Cloud Service Accounts and Logical Datacenters (LDCs) are in scope for the schedule These records are created when you create a Cloud Discovery schedule. They can be missing after an instance clone if the clone is not configured with the correct preservers and exclusions for these tables. 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: ; } } .kb-wrapper-2976976-res { font-family: Lato, sans-serif; max-width: 100%; line-height: 1.7; } .kb-wrapper-2976976-res p { font-size: 12pt; color: #000; margin: 0 0 12px 0; } .kb-wrapper-2976976-res .steps { list-style: none; counter-reset: step-counter; padding: 0; margin: 0 0 16px 0; } .kb-wrapper-2976976-res .steps li { counter-increment: step-counter; display: flex; align-items: flex-start; margin-bottom: 10px; font-size: 12pt; color: #000; } .kb-wrapper-2976976-res .steps li::before { content: counter(step-counter); background: #032D42; color: #63DF4E; font-weight: 700; min-width: 26px; height: 26px; border-radius: 50%; display: flex; align-items: center; justify-content: center; margin-right: 12px; flex-shrink: 0; font-size: 11pt; line-height: 1; } .kb-wrapper-2976976-res strong { color: #032D42; } To resolve this issue, recreate the Cloud Discovery schedule in the Discovery Admin Workspace. This repopulates all required configuration records needed for the schedule to run. Go to Workspaces > Discovery Admin Workspace > Schedules.Select the Cloud Discovery tab and open the affected schedule.Verify that the provider parameter is present. If it is absent, the issue is confirmed.Use the New Discovery option to recreate the Cloud Discovery schedule. For detailed steps on creating a Cloud Discovery schedule, see the Related Links section. 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: ; } } .kb-wrapper-2976976-rl { font-family: Lato, sans-serif; max-width: 100%; line-height: 1.7; } .kb-wrapper-2976976-rl ul { font-size: 12pt; margin: 0; padding-left: 20px; } .kb-wrapper-2976976-rl li { margin-bottom: 6px; } .kb-wrapper-2976976-rl a { color: #032D42; } Manage Cloud Discovery schedules in the Discovery Admin Workspace