Scheduled vCenter Discovery fails at the Discovery Pattern Orchestrator Flow Launcher when the VMware sa_cloud_topology_discovery_pattern configuration record is missing<!-- /*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 vCenter (VMware) Discovery fails, while a horizontal Discovery launched directly against the same vCenter completes successfully. Symptoms Scheduled Discovery for one or more vCenter instances errors out and does not complete.Running horizontal Discovery manually against the same vCenter completes normally and returns CIs.The failure originates in the Discovery Pattern Orchestrator Flow Launcher (flow launch script include).The affected vCenter instances are otherwise reachable and have valid credentials. Cause The Flow Launcher script include used by the Discovery Pattern Orchestrator looks up a configuration record in the sa_cloud_topology_discovery_pattern table for the target. When no matching record exists for the VMware/vCenter path, the script errors on that lookup and the scheduled flow fails before Discovery proceeds. A manual horizontal Discovery bypasses the Flow Launcher path, which is why it succeeds while the scheduled run does not. This commonly surfaces after an upgrade or patch that changes Flow Launcher behavior or removes the expected VMware configuration record. Resolution Run both the scheduled Discovery and a manual horizontal Discovery; confirm only the scheduled (Flow Launcher) path fails.Confirm in the Discovery log that the failure originates in the Discovery Pattern Orchestrator Flow Launcher script include and references sa_cloud_topology_discovery_pattern.Query sa_cloud_topology_discovery_pattern for a record covering the VMware/vCenter pattern and confirm whether the expected record is missing.If the record is missing, engage the owning dev team (Flow Engines / Discovery Pattern Orchestrator) to confirm whether a recent update removed or altered the expected VMware configuration record, and to provide the correct values to restore it.After the configuration record is restored, re-run the scheduled Discovery and confirm it completes.