Predictive Routing Queue Capacity 409 Conflict during Terraform Apply on genesyscloud_routing_queue

Environment:
Terraform v1.6.4
Genesys Cloud Provider v2.12.0
Region: AU (Sydney)

Running into a persistent 409 Conflict when applying changes to genesyscloud_routing_queue. Specifically, updating the capacity attribute for a high-volume queue triggers a conflict with existing active sessions.

Error: Error updating Routing Queue: 409 Conflict
Response body: {"message":"Resource conflict: Queue capacity cannot be modified while agents are logged in or calls are active.","code":"conflict","status":409}

The pipeline runs via GitHub Actions. Pre-check scripts confirm no active calls, but the API still rejects the update. This blocks our nightly IaC synchronization.

Has anyone encountered this specific 409 on capacity updates? Is there a way to force the update via CLI or API directly, bypassing the Terraform provider’s standard retry logic? Looking for a workaround to handle these transient locks during deployment windows in the AU region.

This conflict occurs because the API blocks capacity changes on queues with active interactions. The Terraform provider does not automatically handle this lock. Implement a pre-apply script to pause the queue or wait for active_interactions to reach zero. Alternatively, update the provider configuration to retry on 409 with a delay, though pausing is safer for high-volume queues.

Skip the Terraform retry logic. Use a Genesys Cloud Data Action to push the capacity change to ServiceNow during off-peak hours instead. It bypasses the API lock and keeps your IaC state clean.