Troubleshooting "Run After" discovery - Support and Troubleshooting

Troubleshooting "Run After" discovery Issue  Overview A discovery schedule can be configured to run after the completion of another schedule, for example, so that only a limited set of discovery schedules run at a time. The following figure shows three scheduled discoveries followed by discoveries that are set to "Run After" each respective discovery.

"Run After" enables you to sequentially stagger the schedule. Use this option to run this schedule after the discovery designated in the Run after field finishes. Check the Even if canceled checkbox to designate that this discovery should run even if the Run After discovery is canceled before it finishes.

Note the following:

This option is not valid when the Discovery is started via DiscoverNow, or when using the Discover CI feature. You cannot designate an inactive Discovery schedule. You cannot create a loop by designating the Run After discovery to be the same discovery. This discovery does not run if the Run After discovery does not finish unless the Even if canceled option is selected and the discovery is canceled. Troubleshooting Overview The following flowchart displays the flow from one schedule discovery to the discovery that runs after it.

Important business rules, script includes, and script actions involved in triggering the next discovery are:

Business rule: Discovery - Complete Script Action: Discovery Run Next Script Includes: Discovery, DiscoveryPhaser Troubleshooting steps Confirm that the discovery_status.description is "Scheduled". "Discover Now" and "Discovery CI" will not trigger the next discoveries.

Check that the discovery.complete or discovery.canceled event was created in the sysevent table.

Check that the listed business rules, script includes, and script actions are not customized but match the out of the box versions.

Additional Information See the Create a discovery schedule product documentation topic