Call Flow Export Issues

I'm working on a process to automate migrating Genesys call flows and subordinate object from one ORG to another ORG. I've encountered the following issues:

Using the Terraform export function: Terraform Registry
I have seen some strange behavior when exporting external contacts. The ORG from which I am exporting has very few external contacts, but I am getting an error message stating that the API can only return 1000 records

Using the archy export call flow example:

I've found a single call flow in my test sets that won’t export using archy but will export as a yaml file form the Architect UI. It seems that the flow name has 2 consecutive spaces in it (based on the yaml code exported by the Genesys Architect UI), but in the output from the gc flows list -a command, the flow name only has a single space at that position. archy then reports an error of flow name not found.

Thanks for any and all suggestions.

Hi Craig,

I talked with the dev team. The endpoint that we are calling is CX as Code GET /api/v2/externalcontacts/contacts has a restriction of no more than 1000 records exported at a time. We just put a patch in to issue a warning instead of crashing the export process and that should be out in release 1.18 (which will be released in 1.18).

However, that just keeps the export process from crashing. I talked with the DEV team and they released a GET /api/v2/externalcontacts/scan/contacts endpoint that does not have the 1000 items limit. I have opened a ticket with my team to update our CX as Code externalcontacts provider to use the different endpoint. I do not have an ETA on this yet, so if you need to get this external contact info you might want to use the CLI or the platform API and a script to get this data.

For your second item, are you using Archy or CX as Code to export flows?

Thanks,
John Carnell
Director, Developer Engagement

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.