Discovery Schedule is getting cancelled automatically, but manual run completes successfully

Deebika
Tera Contributor

yesterday

We are troubleshooting an issue where a Discovery Schedule is getting automatically cancelled.

Observed behavior:

  • Discovery runs automatically through the configured schedule → gets cancelled.
  • Manually running the same Discovery Schedule → completes successfully.
  • Manually discovering specific IPs → also works successfully.
  • We are using standard MID Server-based Discovery.

Since manual Discovery works, we are trying to understand what could specifically cause only the scheduled execution to be cancelled.

What should we check to identify the component or process that is cancelling the scheduled Discovery?

Are there any specific Discovery logs, scheduled jobs, cancellation rules/timeouts, system properties, MID Server logs, or Discovery Status records that should be checked?

Any guidance would be appreciated.

0 Helpfuls
  • 79 Views
1 REPLY 1

Mohit 101
Tera Contributor

yesterday

Hi @Deebika ,

Scheduled Discovery failures can happen for different reasons, so I would recommend checking the execution details before identifying a specific root cause.

Since manual Discovery is working, I would focus on the scheduled execution and investigate the following areas:

  1. Discovery Status: Navigate to Discovery > Status. Open the cancelled execution and review the Discovery Log, execution duration, state changes, and last activity before cancellation.

  2. Discovery Schedule: Navigate to Discovery > Discovery Schedules. Check the Max Run Time and Max Idle Time configurations to verify whether any timeout conditions are causing the cancellation.

  3. ECC Queue: Navigate to ECC Queue and check the records around the cancellation time. Look for cancellation-related commands, MID Server communication issues, and any errors in the queue.

  4. MID Server Logs: Verify the MID Server status and review the agent logs around the time of cancellation for communication failures, processing errors, or service restarts.

  5. Discovery Status Monitor: Check the related scheduled job and its execution history to determine whether the Discovery is being identified as inactive or stalled.

  6. Customizations: If the above checks do not identify the issue, review custom Business Rules, Script Includes, and scheduled jobs that might be modifying Discovery execution records or triggering cancellation.

I would also recommend comparing a successful manual execution with a cancelled scheduled execution, especially their Discovery Logs and ECC Queue records.

The key is to identify when the execution changes to Cancelled and correlate that timestamp with the corresponding instance and MID Server logs. This should help narrow down which component is initiating the cancellation.

Without those logs, it would be difficult to confirm a single root cause.

 

Hope this helps! If you find this information useful, please mark it as Helpful and accept it as a solution.

 

Regards,

Mohit

0 Helpfuls