Unable to update Records change from latency to weighted routing

[vgokul984]

We have multiple EKS cluster(1.24) with external DNS(0.13.5) using to create route53 latency based routing with same A record name with different set-identifier with the application name and region. while we tried to change from latency based routing to weighted routing external-DNS is getting crashloop and not working as expected. the external DNS not able to update the existing record with same name on different region which means while we try to update the record on the east with weighted routing it see the same name exists on the west and throughs error "cannot be created as a non-weighted set exists with the same name and type" even though we have set-identifier to differentiate between the region but it works when we remove the both region records it creates newly.:

**need to update the record from latency to weighted routing without deleting the records **:

** update both region ingress annotation value from latency to weighted east with weighted 100 and west with 0 **
Latency annotation:

      external-dns.alpha.kubernetes.io/aws-region: us-east-1
      external-dns.alpha.kubernetes.io/hostname: kubecost.d.ni.test.com
      external-dns.alpha.kubernetes.io/set-identifier: kubecost-useast-1

To weighted annotation on east:

      external-dns.alpha.kubernetes.io/aws-weight: "100"
      external-dns.alpha.kubernetes.io/hostname: kubecost.d.ni.test.com
      external-dns.alpha.kubernetes.io/set-identifier: kubecost-us-east-1

    external-dns.alpha.kubernetes.io/aws-weight: "0"
    external-dns.alpha.kubernetes.io/hostname: kubecost.d.ni.test.com
    external-dns.alpha.kubernetes.io/set-identifier: kubecost-us-west-1

**Environment**: Prod
- External-DNS version (use `external-dns --version`): 0.13.5
- DNS provider: AWS
- Others: Below are the values on the deployements for externaldns

spec:
  containers:
  - args:
    - --log-level=info
    - --log-format=text
    - --interval=30s
    - --source=service
    - --source=ingress
    - --policy=sync
    - --registry=txt
    - --txt-prefix=us-east-1
    - --domain-filter=d.ni.test.com
    - --provider=aws
    image: registry.k8s.io/external-dns/external-dns:v0.13.5

##Error:
when submitting change batch: InvalidChangeBatch: [RRSet with DNS name kubecost.d.ni.test.com., type A, SetIdentifier kubecost-us-west-1 cannot be created as a non-weighted set exists with the same name and type.]\n\tstatus code: 400, request id: 64208896-56f5-47cf-b0c4-bc6f819498e3"
##