Just noticed that updating the dialing_pattern on an active outbound campaign via the Genesys Cloud Provider (v1.36.0) is failing with a 400 Bad Request. The error payload returns {“code”:“bad_request”,“message”:“Invalid dialing pattern configuration for campaign ID 892103”}. This occurs specifically when switching from ‘predictive’ to ‘progressive’ in the Terraform resource genesyscloud_outbound_campaign. The campaign status is currently ‘RUNNING’. I have verified the campaign rules and media types are compatible with progressive dialing. The GC CLI (v2.0.4) shows the same error when attempting a direct PUT request to /api/v2/outbound/campaigns/{campaignId}. The environment is ap-southeast-2. Is there a specific sequence required to pause the campaign before changing the pattern, or is this a provider limitation? I am using Terraform v1.5.7. The configuration block is standard: resource “genesyscloud_outbound_campaign” “main” { name = “Test Campaign” dialing_pattern = “progressive” status = “RUNNING” }. Any insights on bypassing this validation or handling the state change correctly would be appreciated. The logs show no additional context beyond the generic bad_request code.