Discovery status canceled troubleshooting steps

[aaddgg454]

Hi All,

In my client instance, one Discovery status record was canceled due to the Max Run Time limit set on its parent Discovery schedule.

It’s been around 8 days, and the ECC Queue is empty, so I’m unable to trace the exact failure reason directly.

I do have the Discovery logs (5000+ entries), but it's difficult to pinpoint why the schedule suddenly took over 4 hours to run — when it usually completes in about 1 hour — before getting canceled.

Any guidance on how to identify the root cause would be appreciated.

[Mannapuram]

@aaddgg454  Though ECC Queue is empty, you can still sort the Discovery logs by Creation date and look for the first warning message. That might give you the clue. Also, check credentials are working fine. 

[Harish Bainsla]

Hi @aaddgg454  Please follow these steps

1.Check Discovery Schedule Configuration like:

> How many Ip are there in schedule.

> Check if another Discovery schedule was running concurrently so that it will not overlap.

2. Analyze the Discovery Log Entries

> Look for Error, Warning in logs.

> Identify any CI classes or probes that took significantly longer than usual

3.Compare with Previous Successful Runs
Identify what changed:
Were new IP ranges added?
Were credentials updated or failing?
Was a new MID Server used?

4. MID Server Performance
Check the MID Server logs around the same time.
Look for:
High CPU/memory usage.
Network latency or DNS resolution issues.
Errors in agent.log or wrapper.log.

if my answer helps you mark helpful and accept solution