Hi all,
We’re running into a weird issue promoting an Architect flow between environments - specifically, skill assignments are getting dropped during the export/import process. It’s happening consistently. The flow itself comes across fine, all the nodes are there, but any skill associated with a transfer activity is missing on the target org.
It’s not just a visual thing in the flow designer either. When checking the flow’s JSON export, the skill ID is present in the source flow’s definition - it’s definitely part of the exported config. But on the target org, the skillId field within the transfer activity is empty after import. It looks like the import process just ignores this part of the configuration.
We’ve looked at the community posts, and there’s some discussion around data action configurations, but nothing that specifically calls out this behavior with Architect flows. Someone mentioned a similar issue with queue assignments a while back, and the workaround was to manually recreate the skill association in the target org. That’s… not ideal, considering we’re trying to automate this across a number of orgs with CX as Code.
It’s happening with the standard Zoom Contact Center Architect export/import. We’re not using any custom tooling. We tried a basic flow - simple transfer to a skill - and it fails every time. It’s not a complex flow.
Here’s what we’ve tried so far:
- Exported the flow as JSON using the Zoom Contact Center UI.
- Imported the JSON into a separate dev org using the UI.
- Verified the
skillIdis present in the source JSON. - Checked the Zoom Contact Center API documentation for any known issues with flow imports - nothing obvious jumps out.
- Tried exporting as a ZIP file - same problem.
- Compared the flow definition in both environments using the API - confirms skill is missing on the target.
- Verified permissions - the user performing the import has full admin rights.
We’re on Zoom Contact Center, obviously. The flow ID is flow-abcdef1234567890. The skill ID in question is skill-0987654321abcdef.
Anyone else bumped into this? It’s impacting our build pipeline.