Discovery Jobs Not Completing, No ECC Queue Messages<!-- /*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 my Discovery job start but never complete, and no messages appear in the ECC Queue? A: This typically happens when Discovery can initiate the job, but the messages from the MID server are not being processed or inserted into the instance ECC Queue. The job will appear to “hang” without results. Troubleshooting Steps: Check ECC Queue Navigate to System Logs > ECC Queue. Filter for the MID server name. Confirm whether any input or output messages appear when the job runs. Verify MID Logs On the MID host, open agent0.log or agent1.log. Look for lines indicating message delivery attempts and whether the payload is acknowledged. Confirm Connectivity Ensure the MID can resolve and connect to the instance URL (test with curl or Invoke-WebRequest). If the MID is in a restricted network, confirm required firewall/proxy rules. Check Discovery Status Page Open the job’s status page from Discovery Status. If the job starts but never moves past “Sent,” it means the message never entered the ECC Queue. Simulate Payload Copy the payload from the MID logs and simulate it via ECC Queue > New Record to confirm whether parsing errors occur in the instance. Restart or Resync Restart the MID service. If patterns were recently updated, resync patterns to the MID server. Root Cause Examples: ECC Queue table insert failures. Network/firewall blocks preventing MID output from reaching the instance. Corrupted or outdated MID service unable to push payloads correctly.