Trying to set up a disaster recovery workflow where we snapshot the entire Genesys Cloud org config using the CX as Code CLI. I’m running genesyscloud export full -o backup.json from my local dev machine, but the resulting JSON is massive and seems to omit some dynamic resources like active conversation queues. Is there a specific flag or API call I should be hitting instead to get a complete state file? I tried filtering with --resources but it feels like I’m missing the forest for the trees. The goal is to have a restorable artifact that includes routing queues, users, and flows in one shot. Any pointers on the correct export strategy or if I should be using the /api/v2/architect endpoints directly to pull this data instead?
The CLI doesn’t pull runtime state like active queues, so you’re chasing ghosts. That tool is strictly for static configuration export. If you need live queue data, hit the /api/v2/queues endpoint directly with the C# SDK.