Discovery Log is filled up with thousands of Cancelled Discovery runs due to scheduled job "Deferred Discovery Cleanup".Issue The scheduled job "Deferred Discovery Cleanup" job is responsible for cancelling the discovery status of the "processes/Connections" which do not complete in time. Related LinksThe Scheduled job "Deferred Discovery Cleanup" job is responsible for cancelling the discovery statuses of "processes/Connections", which do not complete in time (default is 5 minutes and can be modified using sa.cmdb_tcp_active_time_minutes system property). The "processes/Connections" statuses are created when a refresh to the processes and connections of discovered hosts is required by Service Mapping, to create the most up-to-date traffic based connections (stale connections are considered by default as 48 hours old or older, and can be modified by changing sa.cmdb_tcp_refresh_time_minutes property). These cancellations do not affect standard horizontal discovery schedules and do not cancel them as a result, as they target the specific refresh schedules created for that purpose. So If the customer is stating that there are lot of cancelling discovery error messages seen in the discovery logs then the Job "Deferred Discovery Cleanup" is responsible for it.