Job Running Triggers Not Within Probe Limit

  • KM03771737
  • 13-Jan-2021
  • 13-Jan-2021

Summary

A discovery job is running triggers that are not within its Probe limit.

Error

A discovery job is running triggers that are not within its Probe limit.

Cause

Triggers are not released from a job in the following cases:
 
Cause 1
 
1. ProbeA and ProbeB belong to Cluster1.
2. Range IPs by ICMP is limited to run only on Cluster1. The job runs on both Probes in Cluster1.
3. ProbeB is removed from Cluster1.
4. In the next scheduled run of Range IPs by ICMP, you notice that the trigger is still running on both Probes in the cluster, even though ProbeB no longer belongs to Cluster1.
 
Cause 2
 
1. ProbeA is in Cluster1; ProbeB is under the Default Domain
2. Range IPs by ICMP is limited to run only on ProbeB.
3. ProbeB is added to Cluster1.
4. In the next scheduled run of Range IPs by ICMP, you notice that the trigger is still running on ProbeB, even though ProbeB now belongs to Cluster1.
 

Fix

Deactivate and then reactive the job.