An administrator is troubleshooting why a CMDB CI's last discovered date is not updating after a successful discovery run. The CI is in a valid state and the discovery schedule runs. What could be the cause?
Trap 1: The CMDB identification rule has a condition that excludes this CI…
If the CI is discovered, the condition likely allows matching.
Trap 2: The discovery source is set to 'ServiceNow' but the CI was created…
Discovery source does not affect the update; manual CIs can still be updated.
Trap 3: The CI is a parent class and child class discovery is updating…
Parent CIs can still be updated directly by discovery.
- A
The CMDB identification rule has a condition that excludes this CI from updates.
Why wrong: If the CI is discovered, the condition likely allows matching.
- B
The discovery source is set to 'ServiceNow' but the CI was created manually.
Why wrong: Discovery source does not affect the update; manual CIs can still be updated.
- C
The reconciliation rule is set to 'Manual' and the discovered data conflicts with existing data.
Manual reconciliation prevents automatic updates when conflicts arise, so the date stays unchanged.
- D
The CI is a parent class and child class discovery is updating child records.
Why wrong: Parent CIs can still be updated directly by discovery.