ServiceNow Discovery: Scheduled Jobs starting despite in active=false after clone

[rajeevhanda]

We recently cloned our sub prod instance over production. We have around 16 discovery schedules that are in the active=false state in sub-production. We have even added these into preserve data so that they don't get active=true after clone (as they are active true in production). But after clone, all the schedules ran daily at their scheduled time. But they scan nothing. The count of probes after discovery remains 0 for some (means that discovery is not running correctly) and progressed to some good value which is not expected at all. Can someone tell me what are the probable causes that allow the discovery schedules to run despite they are marked active=false?

Thanks in advance!

[Chris M3]

This is a definite issue that we've experienced, though we haven't pushed ServiceNow on it.   Typically after a clone we go in and mark everything as inactive, then we double check in sys_trigger.list.   You can filter based off I think the document field to find any discovery schedules that are still in the queue to run.

They are likely scanning nothing because the mid server or behaviors point to mid servers that don't exist in sub-production.

[Stephen Farrar]

As Chris alluded to, it's possibly a case of when you mark them as active/inactive scheduled jobs are getting created/removed. So when you clone from prod to subprod, even though your schedules are still marked as inactive - because of your data preserver - the scheduled jobs that are running the discovery on prod are still copied over and executed as normal.

You could consider putting a data preserver in place on sys_trigger if that's where the scheduled jobs are running, which would then prevent those being created also, but you would need to check whether there is anything else thats coming across that way that is needed.

[rajeevhanda]

Yes, discovery does nothing, but the jobs are displayed as active. Last week, I manually marked all the jobs active=false and today I noticed that the jobs are not running at all.

[puchu]

Has anyone got the correct answer?