Stumbled on a weird bug today with genesyscloud_flow resource in Terraform v1.6.2. Applying an IVR flow with a Queue node triggers a 422 Unprocessable Entity error from the /api/v2/architect/flows endpoint. The error payload indicates invalid queue path despite the queue existing and being verified via CLI. This happens only in ap-southeast-2. Has anyone seen this specific validation failure during automated deployment?
Make sure you validate the queue ID format before sending it to the API. In APAC regions, the ID often needs the full organization prefix, not just the short UUID. Check your Terraform variable mapping for missing prefixes.