Clarification on "Most Recent Discovery" Field Updating Daily in CMDB

[Anand Kamale]

Hello Community,

We are investigating an issue related to the Most Recent Discovery (last_discovered) field in the Server table within CMDB/CSDM. The client has observed that this field is updating daily, even for retired CIs, and they would like to understand the source and conditions that trigger these updates.

What We Have Checked So Far:

We have reviewed multiple components, including:

• Transform Maps
• Discovery Schedules
• Business Rules
• IntegrationHub ETL
• Import Sets & Data Sources
• Discovery Logs & Scheduled Jobs
• Scheduled Imports (AWS / AWS Organization)
• Flow Actions

However, we have not been able to identify the root cause of these daily updates.

Findings:

• We came across an article stating that out-of-the-box CIs continue to be discovered regardless of their state.
• If retired CIs should be excluded from discovery, it is necessary to configure Identification Inclusion Rules.
• We also verified that the AWS configuration was neither created nor modified by the COE team.

Request for Assistance:

Can someone help clarify:

1. What are the possible sources that trigger updates to the "Most Recent Discovery" field?
2. Are there additional configurations we should check to prevent retired CIs from being updated?

Any insights or suggestions would be greatly appreciated!

Thank you in advance.

[Mark Manders]

Did you configure the Identification Inclusion Rules to exclude the retired CIs?

Did you check on the transform scripts? 

Are the retired CIs in the import set tables? 

[Anand Kamale]

Thank you for your response.

1. Identification Inclusion Rules – We have not configured any Identification Inclusion Rules yet, so there are no rules explicitly allowing or preventing updates to retired CIs. However, we are still investigating what might be causing the last_discovered field to update daily.

2. Transform Scripts – We reviewed all relevant Transform Scripts, and they are specifically related to the Flexera integration and other unrelated tables. None of them appear to be modifying the last_discovered field for retired CIs.

3. Import Set Tables – We also checked the Import Set tables, and retired CIs are not present in any recent import records, which suggests that external data imports may not be the cause.

Given these findings, we are still looking for potential sources that could be updating the last_discovered field. Do you have any suggestions on other configurations or processes that might be contributing to this?

Appreciate your insights!

[Community Alums]

Hi @Anand Kamale , 

Just few more thoughts here: 

You need to find exact update timestamp in the audit logs for the most recent discovery field while comparing multiple components like  Business rules, Discovery and any other import logs. 

Is the update to this field happening on daily basis around same time? Please check this out, incase if you haven’t already. 

Regards, 

srinija