Can anyone explain why the POST to /api/v2/architect/flows returns 400 Bad Request during Terraform apply?
The payload contains a valid Data Action reference to a FastAPI endpoint. GC CLI v2.0.8. Terraform v1.7.0.
The error payload indicates ‘invalid action type’. The action works manually in Architect UI. HCL config is attached.
According to the docs, they say that data action definitions must be fully resolved within the flow structure before deployment, not just referenced by ID. When using Terraform, the platform expects the complete action configuration object to be present in the JSON payload, including the specific endpoint URL and method details. If the HCL module only provides a reference ID, the Architect service returns a 400 error because it cannot validate the action type during the initial schema check. You should ensure the data action block includes the full specification rather than relying on external resolution. This often happens when the Terraform state is out of sync with the actual Genesys Cloud configuration. Verify that the data action is created and confirmed active in the Admin console before attempting the flow update. The performance dashboard can also show if the action is failing at runtime, which helps distinguish between deployment issues and execution errors.
The root cause here is the deployment payload missing the full schema definition. When automating, data_action references alone are insufficient. Include the complete endpoint_url and http_method within the flow JSON. The API validates structure strictly, similar to how bulk exports require explicit metadata. Check the actions array for completeness.
TL;DR: Confirmed.
If I remember correctly… the bulk export endpoint is notoriously picky about payload size, especially when dealing with screen recording metadata which is heavy. while the search api scroll method mentions pagination limits, the data action payload validation seems to enforce that same strictness on structure completeness.