Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Archy Import Call Flow with Exit Error code 100

  • 1.  Archy Import Call Flow with Exit Error code 100

    Posted 06-05-2025 18:43

    saravana.n.kumar | 2021-10-12 14:43:34 UTC | #1

    Team - I am moving a call flow from one org to another org using CX as Code i am almost through in this.

    All objects are successfully created, when yaml file is getting published i am getting following error in YAML

    2021-10-11T16:05:43.940Z: Command: 'publish' 2021-10-11T16:05:43.941Z: unable to find 'Queue' on the action 'dataTableLookup'. YAML: Skill: var: "Flow.skill" Priority: var: "Flow.priority" Queue: var: "Flow.Queue"

    i resolved this error in yaml code one of the header is missing it is configured as identifier.

    i followed the example usage given in below for data table properties .

    But Working config as below not sure why the identifier is mandate in this config.

    could you please clarify why identifier is being used ? post the above config Archy was able to publish the call flow in destination Org.

    John_Carnell | 2021-10-12 16:01:29 UTC | #2

    HI Saravana,

    A couple of things:

    1. You need to make sure that the queue name being referenced in your Archy YAML file matches the name of the queue being created.
    2. Since Archy is a command-line tool being called from your Terraform flow, it will not participate in the dependency graph that Terraform puts together. This means you have to explicitly control the order of dependencies between pre-flow deployment (e.g. queues) and post-flow deployment (e.g. the trigger that will actually invoke the flow.

    For example, if you look at the blueprint that I originally wrote as an example of CX as Code, you will see that I explicitly define the modules that must be run first before the Archy flow.

    Now if you are using a CI/CD pipeline you can simplify things by not having the Archy script be invoked in Terraform directly. I am working on a blueprint that is in draft status right now that integrates CX as Code and Archy into a GitActions job. That draft can be found here. If you look at the GitAction workflow in this draft blueprint, you can see I install Archy first, then run CX as Code (without any of the flow dependencies) and then run Archy as the next step in the pipeline.

    I hope that helps and please post if you are still having issues.

    Thanks, John Carnell Manager, Developer Engagement

    saravana.n.kumar | 2021-10-12 17:48:15 UTC | #3

    Thanks John it helps. We are implementing CICD Pipeline using GitHub-->Jenkins-->Terraform-->Genesys Org ( 3 Genesys ORG we are having Dev-Test-Prod.)

    We would like to have a Devops with Genesys Cloud.

    John_Carnell | 2021-10-12 17:51:51 UTC | #4

    Hi Saravana,

    Awesome. I hope the CICD pipeline works as an example. We are working on a more native integration with Archy/Lambda's that will eliminate the need to call out to the Archy CLI, but that is still in development. Always welcome feedback too (good or bad) on CX as Code as my team is currently doing the development and support for it.

    Thanks, John Carnell Manager, Developer Engagement

    system | 2021-11-12 17:51:57 UTC | #5

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

    This post was migrated from the old Developer Forum.

    ref: 12329



Related Content