Scheduled VMware vCenter Discovery ends in Cancelled status with no ECC dispatch — Flow Launcher references a missing sa_cloud_topology_discovery_pattern record<!-- /*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 Scheduled VMware vCenter Discovery completes with a Cancelled status and no ECC dispatch, while manual horizontal Discovery against the same target succeeds. Symptoms A scheduled vCenter Discovery runs for 6–9 hours and then ends with a Cancelled status.No records are dispatched to the ECC queue for the scheduled run.Manual/horizontal Discovery launched directly against the same vCenter target completes normally.The MID Server has network access to the VMware environment only; no other cloud schedules run on it. Cause The Flow Launcher script used by scheduled cloud Discovery references a configuration record in the sa_cloud_topology_discovery_pattern table that does not exist for VMware. With the record absent, the Flow Launcher errors before any ECC dispatch occurs, so the schedule terminates in a Cancelled state with nothing queued. Manual horizontal Discovery does not use the Flow Launcher path and is therefore unaffected. This behavior is associated with DEF0446210 / PRB1701504 (fixed Washington DC) and DEF0260054 / PRB1541448 (fixed San Diego). Resolution Confirm the failing run is the scheduled (Flow Launcher) Discovery path and that it ends Cancelled with no ECC output, while manual Discovery succeeds.Inspect the sa_cloud_topology_discovery_pattern table for the VMware configuration record the Flow Launcher expects, and confirm whether it is missing or was removed.If on a release predating the fix, plan an upgrade/backport to a release carrying DEF0446210/PRB1701504 (Washington DC) or DEF0260054/PRB1541448 (San Diego) as applicable, or engage the owning dev team (Dev-Flow Engines) to restore the corrective config record.Re-run the scheduled Discovery and confirm ECC dispatch resumes and the schedule completes successfully.