We’re trying to migrate our Architect flows to a Git repository using the CX as Code CLI. The goal is to get a full export of all flows as JSON files so we can version control them alongside our Terraform state.
The command seems to work fine for small test environments, but in our production org (which has ~150 flows), the genesyscloud architect flow export command hangs indefinitely after downloading about 40% of the flows. The CPU usage spikes, then drops to zero, and the terminal just sits there with no output or error message. I’ve left it running for 3 hours.
Here’s the command we’re using:
genesyscloud architect flow export \
--output-dir ./flows \
--filter-id "*" \
--verbose
The logs show it successfully fetching individual flow definitions via /api/v2/architect/flows/{id}, but then it stops. No HTTP 500s, no timeouts. Just silence.
Environment specs:
- CX as Code CLI version: 1.14.2
- OS: Windows 11 (WSL2 Ubuntu 22.04)
- Genesys Cloud Org: Production (150+ flows, complex sub-flows)
- Memory: 16GB allocated to WSL
I’ve tried:
- Adding
--max-retries 5to the command - Exporting flows in smaller batches using
--filter-idwith specific regex patterns - Running the export on a local Mac instead of WSL (same result)
The JSON payloads for the successful downloads look correct. Each flow is saved as a separate .json file with the proper structure.
Is there a known limit on the number of flows that can be exported in a single run? Or is this a memory leak in the CLI?
{
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"name": "Main IVR Entry",
"description": "Primary entry point for voice interactions",
"version": 12,
"type": "voice"
}
The verbose output stops at this point:
2024-05-15T14:32:11.123Z [INFO] Fetching flow: Main IVR Entry (a1b2c3d4...)
2024-05-15T14:32:12.456Z [INFO] Successfully exported flow: Main IVR Entry
2024-05-15T14:32:13.789Z [INFO] Fetching flow: Secondary Menu (b2c3d4e5...)
Then nothing. No more logs. No exit code.