Genesyscloud_messaging_webmessenger 409 Conflict on AU-1 BYOC

General Discussion
1

Is it possible to update the genesyscloud_messaging_webmessenger resource without triggering a 409 Conflict on our AU-1 BYOC instance? The deployment pipeline is failing during the apply phase.

  • Environment: AU-1 BYOC
  • Provider: genesyscloud v1.22.0
  • Pipeline: GitHub Actions
  • Resource: genesyscloud_messaging_webmessenger

The Terraform plan succeeds, but the apply step fails with a 409 Conflict. The error indicates a resource version mismatch.

Error: Error updating Web Messenger: 409 Conflict
Message: Resource version mismatch. Expected version 12, current version 13.

The configuration is minimal. Only the name and description are being updated.

resource "genesyscloud_messaging_webmessenger" "main" {
 name = "Web Messenger - Production"
 description = "Updated description for v2.1"
 
 # Other static config omitted for brevity
}

We have verified that no other pipelines are running concurrently. The GitHub Actions runner is isolated. The 409 suggests the resource state in Genesys Cloud has changed since the plan was generated. This is unusual for a simple update.

We are using the genesyscloud provider version 1.22.0. The documentation suggests that updates should be idempotent. However, the 409 error persists across multiple runs.

Steps taken:

  • Verified the resource exists in the Genesys Cloud UI.
  • Checked for concurrent deployments in GitHub Actions. None found.
  • Attempted a terraform refresh before apply. No change in outcome.
  • Reviewed the provider release notes for v1.22.0. No known issues with web messenger updates.

The error log from the GitHub Actions run shows the following sequence:

  1. Read current state.
  2. Plan updates.
  3. Apply updates.
  4. Receive 409 Conflict.

Is there a specific way to handle optimistic locking for this resource? Or is this a known issue with the AU-1 BYOC environment? We need a workaround to ensure our CI/CD pipeline is stable. The current failure rate is impacting our release schedule.

Any insights on how to resolve this version mismatch would be appreciated. We are considering switching to API calls directly if Terraform cannot handle this reliably.