Discovery is not setting older tomcat instances to "Absent" stateIssue Some "Tomcat" instances are neither deleted nor their "state" is set to "Absent," though their "Most Recent Discovery" is not the latest. What is the expected behavior for these kinds of records which are discovered sometime in the past but present any more. CauseTomcat instances are discovered by ADM Probe.Patterns have something called "delete strategy" that allows them to detect when something that was previously discovered, which is related to the Main CI of the pattern, goes missing.This is why some of the records like storage disks, network adapters, etc. as set to Absent, or delete them automatically when they are no longer being discovered for a given Linux server (using linux server as an example).Since the Tomcat Instances are discovered by ADM Probe and there is no "delete strategy" for ADM at the moment.If the process doesn't show up in the ADM result probe, the Tomcat pattern for it simply won't launch, and there is no "delete strategy" that will take place and mark it as absent/delete/etc.This should be the case for other applications as well.ResolutionDue to this behavior being consistent for pretty much all applications, the below steps can be tried to either mark the CIs as "Absent" or delete. For tomcat servers, create a scheduled job that goes over the cmdb_ci_tomcat_server table and marks them as absent if they haven't been discovered/updated recently.This, in conjunction with the table cleaner, will clean up the old records that aren't being discovered anymore.Also, for other application types, please create a similar scheduled job on cmdb_ci_appl, and do the same rules for marking as absent.Use "staleness rules" as a potential option that would accomplish something similar to the scheduled jobs mentioned above.