Terraform plan drift on genesyscloud_routing_queue with state lock error

Why is my terraform plan showing massive drift on genesyscloud_routing_queue resources even though nothing changed in the code?

I’m running the Genesys Cloud Terraform provider v1.65.0. The state file seems corrupted or locked by a previous failed run, but I can’t refresh it. Every time I try to run terraform refresh or plan, I get this error:

Error: acquiring the state lock

Error message: ConditionalCheckFailedException: The conditional request failed
Lock Info:
 ID: 8f3a2b1c-9d4e-5f6a-7b8c-9d0e1f2a3b4c
 Path: tfstate/genesyscloud.tfstate
 Operation: OperationTypeRefresh
 Who: crm@devbox
 Version: 1.65.0
 Created: 2023-10-27 14:32:01.000000 +0800 UTC
 Info: 

The queue definitions in my .tf files match the current state in the Genesys Cloud admin UI exactly. I’ve tried terraform force-unlock with the ID above, but it says the lock doesn’t exist. The remote state backend is S3.

Is there a way to bypass this lock and force a state sync without manually editing the JSON state file? Or is the provider caching something locally that’s causing the drift detection to fail?