Best practice while working with auto scaling groups

I rolled out blue/green deployment that leverages aws codedeploy and aws auto scaling groups. During the deployment, codedeploy recreates the scalinggroup. As the result re-running TF code attempts to create the original group.
Adding a “lifecycle” hook, doesn’t make a difference.

What is the best practice in the situations when for the original resource got recreated outside TF control, BUT TF should not “restore” the resource during a consecutive runs?