CX as Code CLI: Architect flow export failing with 400 Bad Request on complex sub-flows

General Discussion
1

We are attempting to export our entire Architect flow library to JSON for a state backup using the CX as Code CLI. The standard documentation suggests using the genesys-cloud cxascode export command with the --resource-type architect-flows flag.

The execution works fine for simple flows, but it consistently fails when it encounters flows with nested sub-flow actions or complex routing logic. The CLI returns a generic 400 error without pointing to a specific node.

Here is the command we are running:

genesys-cloud cxascode export \
 --resource-type architect-flows \
 --output ./exports/architect-backup \
 --environment prod

The error log captures this payload:

{
 "errors": [
 {
 "message": "Invalid flow structure detected during serialization.",
 "code": "400",
 "context": {
 "flowId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
 "stepId": "step-123"
 }
 }
 ]
}

We have verified the flow is active and valid in the UI. Is there a known limitation in the CLI exporter regarding certain node types, or is there a specific flag to bypass validation during export?