Why does this setting in the genesyscloud CLI seem to ignore the --include-all flag when exporting Architect flows with complex data actions?
I am running the CLI v2.8.1 in a Berlin-based CI pipeline (Europe/Berlin). The goal is to version-control the entire Architect configuration. I expect a complete JSON dump of every flow, including nested sub-flows and all associated data actions. Instead, the output JSON is malformed. Specifically, flows with more than 50 steps or complex regex patterns in data actions result in truncated strings or missing steps arrays entirely.
Here is the command I am running:
genesyscloud arch flow export --output-dir ./flows --include-all --format json
The resulting JSON for a specific flow (flow-id-12345.json) looks like this:
{
"id": "flow-id-12345",
"name": "Complex_Validation_Flow",
"steps": [
{
"id": "step-1",
"type": "queue",
"settings": {}
}
],
"dataActions": {
"id": "action-99",
"expression": "// TRUNCATED //"
}
}
The dataActions expression is cut off. I verified the raw API response via Postman using GET /api/v2/architect/flows/flow-id-12345. The API returns the full JSON payload without truncation. The issue is isolated to the CLI’s serialization or buffer handling.
Error: JSON parse error at line 45, column 12: unexpected end of string
This occurs during the jq validation step in my pipeline. I have tried increasing the --max-depth flag, but it does not exist in the current CLI version. Is there a hidden config option for chunking large exports? Or is this a known bug in the exporter module? I need a workaround to get valid JSON for Terraform import. No workarounds involving manual API calls; I need CLI automation.