Discovery Agent Stuck in "Collecting" Though Test Check Works<!-- /*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; } } Q: Why does Discovery stay stuck in Collecting when the Agent test check passes? A: This usually indicates that the agent can communicate with the MID, but the payload is not being inserted into the instance. The MID and agent are working, but something is blocking data from reaching the CMDB. Troubleshooting Steps: Confirm the test check succeeds (use uptime Metric or similar). Check the agent logs for evidence that payloads are being generated. Review the MID logs and ECC Queue. Retrieve the payload from the ECC Queue and simulate it in the instance to see if errors occur. Check the System Logs in the instance for insert errors related to the agent. Filter by the agent name to narrow results.