Thanks for the answer! This makes sense. It is a bummer though that the auditing gets "spammed" with daily Install status changes and I cannot find a way to exclude this audit.   An idea I had is that If the import was using a kind of staging table (that was emptied after every run) it could use a GlideRecord query to compare the CMDB with the staging table. If the CMDB has CIs with Discovery Source = SG-Meraki that is not in the staging table, it could change the install status of those CIs to Retired and keep the rest as Installed. That way only the missing CIs would have their CI status changed to Retired. ... View more