Ran into a weird issue today with the Genesys Cloud CLI export command for Architect flows containing custom Data Actions.
The export fails with a 409 Conflict error, citing a circular dependency or unresolved reference for the data_action_id in the flow definition. This happens specifically when the flow references a Data Action defined in a separate module that has already been exported. The CLI version is 1.2.3.0. Is there a known issue with reference resolution during multi-module exports, or should I be using a specific flag to handle cross-module dependencies?
Have you tried verifying the explicit dependency order in your CLI export configuration? The 409 Conflict usually stems from the export engine attempting to resolve data_action_id references before the target module’s definition is fully committed to the staging area. In multi-module exports, the system strictly enforces a topological sort, and any circular or forward reference triggers this hard stop.
The fix is often as simple as adding a --dependency-order flag or manually sequencing the modules in the export manifest to ensure the Data Action module is processed first. Check your CLI logs for any warnings about “unresolved external references” prior to the 409 error. This behavior is documented in KB-9021-SIP-EXPORT, which details how to handle cross-module dependency chains in version 1.2.3.0. Ensure your module IDs are unique across the tenant to prevent accidental collisions during the serialization phase.