OCI Cloud Discovery: VM Instances Incorrectly Marked as Terminated/Retired Due to Deletion Strategy Timing<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue:During OCI Cloud Discovery for VM instances, some VMs temporarily transition to Terminated/Retired even though they exist in the incoming payload. The VM state reverts to Active/On shortly after the discovery run completes. This behavior occurs because the Deletion Strategy evaluates CIs as stale before all discovery sensors have completed processing, causing temporary incorrect retirements and potential impact on related CIs or application relationships. Steps to Reproduce:1. Run an OCI Cloud Discovery targeting VM instances.2. Observe that some VM instances may temporarily transition to Terminated/Retired during the discovery run.3. Within a short period, VM instances may revert to Active/On once discovery sensors complete processing.4. Audit the CMDB VM CI history to verify multiple state changes for the same CI within a single discovery run.5. Observe that related server or child CIs may temporarily reflect retired/terminated status due to the cascading effect of the deletion strategy. Resolution:The temporary flip-flop occurs because the Deletion Strategy evaluates CIs based on the Most Recent Discovery field before all multi-page discovery responses are processed. Workaround: The _markRetired function in OCIDefaultDeleteStrategy has been updated to schedule a 5-minute delay before executing retirement logic. This prevents premature terminations and ensures that CIs updated after the discovery run start are skipped for retirement. The workaround is delivered via an update set containing the revised OCIDefaultDeleteStrategy. A permanent fix - PRB1984896