Deletion Strategy is not invoked during GCP Events-based Discovery, leaving related records behind for Terminated VMsDescriptionRelated records are not deleted when a GCP virtual machine instance is terminated through event-based discovery. cmdb_key_value records are still present for VM instances that are no longer operational or have already been terminated.Behaviour is specific to event-based discovery (based on a cloud event in sn_cmp_cloud_event), where a deletion is not triggered for related records when the virtual machine instance is terminated. It works fine on a Horizontal discovery where a deletion strategy gets invoked.Steps to Reproduce Discovery a Google Cloud (GCP) VM using Horizontal Discovery, to create all the records, including cmdb_key_value Via GCP, Terminate the VM. This will trigger a Cloud Event [sn_cmp_cloud_event], and Event-based Discovery Expected behaviour:As with Horizontal Discovery, related records should be cleaned up. Actual behaviour:cmdb_key_value records are still present for VM instances that are no longer operational or have already been terminated. When performing event-based discovery, the onus then falls on the customer to identify and maintain a way to clean up that data that would have otherwise been cleaned up automatically through horizontal discovery. Check Key Value pairs on/cmdb_ci_vm_instance_list.do?sysparm_query=state%3Dterminated%5Eoperational_status%3D2%5Einstall_status%3D100%5Ediscovery_source%3DServiceNow%5Esys_class_name%3Dcmdb_ci_vm_instance%5Emanufacturer%3Dd048bbb26fbef900c423884f8e3ee45a&sysparm_view=WorkaroundAfter carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to address this issue as a future product enhancement. The customer would currently need to identify and maintain a way to clean up that data that would have otherwise been cleaned up automatically through horizontal discovery.Related Problem: PRB1646613