The terraform plan consistently fails when deploying updates to a scheduled workflow using the Great Cloud Orchestrator. Specifically, the workflow execution timeout parameter - defined as 600 seconds in the workflow_execution_settings block - appears to be ignored.
We’ve confirmed the API call - /api/v2/workflows/{workflowId}/settings - is being constructed correctly, and the timeout value is present in the terraform plan output. However, the workflow still terminates after the default 300-second timeout. The provider version is 1.25.3, and we’re testing within a dedicated EU-West sandbox.
It’s curious, because manual updates via the Genesys Cloud UI respect the configured 600-second timeout. Is there some interaction between the Orchestrator and the Workflow engine that isn’t correctly reflected when applying changes through terraform?