Agent Script Version Drift During Terraform Apply

General Discussion
1

How should I properly to handle script version conflicts when deploying via genesyscloud_outbound_campaign?

Running terraform apply with provider version 1.45.0. The deployment pipeline fails consistently with a 409 Conflict error. The API response indicates that the script version in the state file does not match the version currently published in Genesys Cloud.

The Terraform state shows version v1.2.0, but the Genesys Cloud UI shows v1.2.1. This discrepancy occurs after a manual update in the UI for testing purposes, which was never reflected in the code repository. Running terraform refresh does not resolve the mismatch. The genesyscloud_outbound_campaign resource attempts to force the old version, causing the deployment to abort.

Current workflow:

  1. Manual script update in UI.
  2. terraform refresh runs.
  3. terraform apply fails with 409.

Is there a specific flag or sequence to force the local state to align with the remote version without deleting the script resource? The documentation suggests using depends_on for ordering, but that does not address the version hash conflict. Need a clean method to reconcile this without destroying and recreating the outbound campaign.