Genesys Cloud - Developer Community!

When registering a call flow using Archy, an issue occurs when the flow contains Data Actions: some properties of the Data Action are missing.

If I edit the relevant property from the call flow editing screen of Architect, the registered content is displayed and can be saved.
I think this is likely a bug in either Archy or the call flow registration functionality of Genesys Cloud.

Best Regards,

Mikio

Hello @Mikio Enomoto,

You're right to suspect this could be a bug - I've actually seen similar behavior with Archy and Data Actions before. It seems like there's an issue with how Archy serializes/deserializes certain Data Action properties during the export/import cycle.

From what I understand, when you export a flow to YAML that contains Data Actions, Archy sometimes doesn't capture all the configuration details - particularly things like input/output mappings, certain contract properties, or timeout settings. But here's the interesting part: the Data Action reference itself is intact, which is why when you open it in Architect's UI, it can re-hydrate those missing properties from the actual Data Action definition that exists in your org.

I'd recommend trying a couple things:

First, double-check your Archy version - they've fixed quite a few Data Action-related issues in recent releases. Run archy version and see if you're on the latest. There were some specific fixes around Data Action property handling in the changelog.

Second, when you're working with the YAML file, you might need to manually define some of those Data Action properties that should have been there. Look for the callData action in your YAML and make sure properties like inputs, outputs, timeout, and any custom configuration are explicitly set. Sometimes Archy expects these to be fully specified even if they're already configured in the Data Action itself.

Third, if you're moving flows between orgs, keep in mind that Data Actions are referenced by name, so even if the Data Action "exists" in the target org, any subtle differences in the contract (schema changes, new fields, etc.) can cause properties to appear missing.

As a workaround until this gets fixed, you could try:

 - Export the flow from Architect
 - Open it in Architect (not Archy) in the source org
 - Make a trivial change and save to force Architect to serialize everything properly
 - Export again and see if the YAML is more complete

Would definitely suggest opening a case with Genesys support about this though - include your Archy version, a sample YAML snippet showing the missing properties, and mention that manually editing in Architect fixes it. That'll help them track down whether it's an Archy export issue or a flow import/registration issue.

Let me know if any of that helps!