Discovery Cancellation Process Overview - Support and Troubleshooting

Discovery Cancellation Process Overview Description border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border- spacing:2; } table.internaltable { white- space:nowrap; text- align:left; border-width: 1px; border-collapse: collapse; font- size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } table tr td { padding: 15px; } .title { color: #D1232B; font- weight:normal; font- size:28px; } h1{ color: #D1232B; font- weight:normal; font- size:21px; margin- bottom:-5px } h2{ color: #646464; font- weight:bold; font- size:18px; } h3{ color: #000000; font- weight:BOLD; font- size:16px; text-d ecoration:underline; } h4{ color: #646464; font- weight:BOLD; font- size:15px; text-decoration:; } h5{ color: #000000; font- weight:BOLD; font- size:13px; text-decoration:; } h6{ color: #000000; font- weight:BOLD; font- size:14px; text-decoration:; } hr{ border-top-width: 1px; border-top-style: solid; border-top-color: #cccccc; } ul { list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> A discovery schedule can be configured to have a "max run time". The discovery will be automatically cancelled if this max run time is reached.

Discovery Cancellation Process Overview A couple of important script includes are called when a discovery is created:

Discovery StartDiscovery StartDiscovery creates a scheduled job(sys_trigger record) to cancel the discovery. The following is an example scheduled job created to cancel a discovery:

The scripts will also log to "System Logs" that the discovery will be cancelled and at what time:

Troubleshooting If the discovery is not cancelled as expected, the following can be done for troubleshooting.

Check that script includes Discovery and StartDiscovery are OOB. Check that the cancellation scheduled jobs are being created as expected, a test discovery can be run to confirm this. Search the "System Logs > System Log > All" for "Cancelling Discovery " (replace with the actual discovery number). If the "Cancelling Discovery ..." message is found, then the mechanism to cancel the discovery was successful. Check that there were no performance issues at the time the discovery should have been cancelled and that the workers were not behind (unlikely to happen). Additional Information Related to this topic:

How to troubleshoot a cancelled Discovery in case of max run time window has been exceeded