Discovery Pattern Fails with Error "Cluster_id Not Found"<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Question: Why does a Discovery pattern fail with the error “Cluster_id not found”? Answer: This happens when Discovery is targeting a Kubernetes or cloud environment but no valid cluster is returned from the Service Account. In the pattern flow, Step 4 is expected to retrieve cluster information, but if nothing is returned, later steps (such as Step 6) fail with “Cluster_id not found”. Troubleshooting Steps: Review the Discovery logs for the error “Cluster_id not found”. Confirm that Step 4 of the pattern returns a valid cluster. If the Service Account has limited permissions, cluster data may not be available.