Change request for Discovery Job dispatch logic

Change request for Discovery Job dispatch logic

UCMDB restarts all active discovery jobs after following operations regardless of their discovery schedules.

   - UCMDB server restart 

   - Making changes on discovery jobs

   - First activation of jobs.

   - And so on.


Above situations are not desirable because most customers want the jobs to run at the scheduled time only - usually during non-business hours.

So we need to have an option for probe to strictly obey discovery schedules.


Trusted Contributor.. mlukezic Trusted Contributor..
Trusted Contributor..

We have experienced the same behaviour.  The majority of our discovery jobs are scheduled to run with staggered start times by entering a Start Date (and time) in Discovery Scheduler.  Then, at some point, one or more of our probes will show (in JMX) all jobs starting at the same random time.  We don't know what causes this, wether some action listed above or something else.  We have not been able to consistently trigger the problem.

We opened a similar Enhancement Request in the past requesting an explicit Start Time (not just Start Date) but the QCCR was deferred.  Maybe this time it will get more traction.

Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor


from my point of view the desired behavior is already implemented since long time.

definitely, if you activate a job, the discovery will not trigger immediatly on all CIs in the job. it will just put the status of the trigger CIs to "reached probe" and the execution will wait for the scheduled time from the job properties.

the only exception is if you have checked "invoke on new triggered CIs immediately", in this case the discovery will immediately start once a CI has been added to the job.

if this does not work in your environment, it is a defect and a support ticket should be opened instead.



The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.