Exclude Retired Stale Service Accounts from DiscoverySummaryBackground:When users discover the same service account again using cloud discovery, a few deleted service accounts will not come under the obtained service account. Our previous approach was to still store those deleted accounts and every time discovery runs on the master account, it was trying to discover the resources from those already deleted service accounts. Ideally, we should not discover those service accounts. Users can discover the resources using the master / member account feature of the cloud discovery. When user discovers any master account/management group/folder, it will also fetch all the related member accounts/ subscriptions / projects in case of cloud discovery. When users re-run the discovery, we are updating the newly added service accounts in our table (cmdb_ci_cloud_service_account) but we are not marking the service accounts install status as Retired which were present before but not present now. Fix:When users re-run the discovery on the selected service account, we will compare the list of already added service accounts in our table with the list we got from our latest discovered sub accounts. If we find any sub account which was present before and is not available in the latest discovery, we will update the install status as retired. ReleaseUP2 and VInstructionsTo enable this feature customer has to create a new Property by Navigating to All -> System Properties -> All Properties with name "glide.discovery.retire_stale_accounts" and set it to true.The reference can be taken from the screenshot attached to the KB.Now there are two scenarios:1. If the property "glide.discovery.auto_refresh_ldc_and_sub_account" is enabled then from next Cloud Discovery Scheduled Run, all the stale service accounts will be marked as "Retired" in "cmdb_ci_cloud_service_account" table and removed from "cmp_discovery_ldc_config" for that particular schedule to avoid running discovery for those stale accounts.2. If the customer is editing an already existing schedule or making a new one and manually does "Refresh" from CDU UI, all the stale service accounts will be marked as "Retired" and further will be removed from "cmp_discovery_ldc_config" when customer goes on to click on "Finish/Finish & Save" for that particular schedule. This scenario doesn't take into account value of property "glide.discovery.auto_refresh_ldc_and_sub_account" as this action is manual by customer for a schedule.Related LinksThe property "glide.discovery.retire_stale_accounts" is an undocumented property (i.e. it is not OOB) and customer has to create and enable it manually for this feature to be enabled.