Hi,
I have discovery schedules set up for our AWS and Azure environments. I noticed that when VMs are off then deleted from Azure or AWS, often VM instance CIs are stuck in off state instead of terminated
I checked the related CI types table and deletion strategy is marked as retired for but AWS and AZure pattern. What do I miss?
