Launching CMPv2 Cloud Discovery from Discovery Schedules does not create any ProbesIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms When launching CMPv2 Cloud Discovery from Discovery Schedules (Cloud Resources), a Discovery Status is created but no ECC Queue records are created. The Discovery Status will stay stuck in 'Started' state and never completes. Release Jakarta and newer releases. Cause This happens when user generates multiple Discovery schedules from the same Service Account. Only newest generation will have a properly linked Discovery Config. Discovery logic will look for this Discovery Config before launching the probes. If Discovery is kicked off from the older generated Discovery Schedule(s), Discovery logic won't be able to find the Config and thus no probes are launched. Resolution - Delete all Cloud Resources discovery schedules generated from the Service Account and regenerate a new one.