Genesys Cloud - Developer Community!

 View Only

Sign Up

  • 1.  scripted Architect export error on a couple of flows

    Posted 4 days ago

    I'm working on a script to export my flows programatically for each of our orgs to make routine flow backups more efficient.  Overall it's working but two of my flows are encountering this error during the Archy export:

    TRACE:[architect.FlowReferenceProperty] missing flowInfoViewModel for id:bc18e...

    The issue happens whether I am backing up as yaml or architect file.  The flows are valid inbound call flows, and one is in production.  I performed a dependency rebuild in case there was a dependency issue but no change.  All other inbound, in-queue, voice survey flows back up with no issue in this org.  I  haven't tried another org as this one is small and clean, an ideal candidate.


    #PlatformCLI

    ------------------------------
    Vikki Papesh
    Principal Genesys Cloud Developer
    Tandem Diabetes Care, Inc.
    ------------------------------


  • 2.  RE: scripted Architect export error on a couple of flows

    Posted 3 days ago

    Hi Vikki,

    The error looks like Architect is trying to resolve a flow reference that no longer has valid metadata available during export:

    TRACE:[architect.FlowReferenceProperty] missing flowInfoViewModel for id: <id>

    Since the flows validate, publish, and execute correctly, I'd suspect either a stale/orphaned reference (subflow, common module, transfer target, etc.) or a metadata inconsistency specific to those flows rather than an issue with your export script.

    Have you checked whether the GUID in the trace maps to another flow or Architect resource? That might help identify the missing reference. Otherwise, this may be worth raising with Genesys Care along with the flow IDs and Archy debug logs,



    ------------------------------
    Cesar Padilla
    INDRA COLOMBIA
    ------------------------------



  • 3.  RE: scripted Architect export error on a couple of flows

    Posted 3 days ago

    I exported all the flows and there is no matching GUID there.  Is there an easy way to parse the entire org for a specific GUID?  The flow is linked to queues, data tables, schedule groups, prompts, schedules, etc.  That's why I did a dependency update, but without knowing what I am looking for when flow validation shows no issues, it's hard to figure out where to look first.



    ------------------------------
    Vikki Papesh
    Principal Genesys Cloud Developer
    Tandem Diabetes Care, Inc.
    ------------------------------

    Original Message


  • 4.  RE: scripted Architect export error on a couple of flows

    Posted 3 days ago

    Hi @Vikki Papesh,

    Unfortunately, there isn't a native "search this GUID across the entire org" capability that I'm aware of.

    A couple of things I would try:

    • Run an Architect export in JSON/YAML (for the flows that do export successfully) and perform a text search for the GUID across the exported artifacts. Sometimes the reference is buried in a task, reusable task, transfer action, data action, schedule check, or a resource that isn't obvious from the Architect UI.
    • Use the Dependencies view in Architect and compare one of the failing flows against a similar flow that exports correctly. If the missing flowInfoViewModel points to a FlowReferenceProperty, I'd focus on anything that references another Architect object (subflows, common modules, menu transfers, call flow transfers, etc.).
    • If you have Platform API access, you could also query the various Architect resources (flows, prompts, schedules, schedule groups, data tables, bots, queues) and search for the GUID programmatically, although that can be a bit tedious if the underlying reference is no longer resolvable.

    The part that stands out to me is that the error specifically mentions:

    architect.FlowReferenceProperty

    which makes me think Archy is attempting to hydrate a flow-related reference during export and can't retrieve the corresponding metadata object. If the flow validates and runs normally, this could be an orphaned internal reference that validation is not checking but the export process is.

    At that point, I agree this may be worth a Genesys Care case. Providing the affected flow IDs, the missing GUID from the trace, and the Archy debug logs should help Engineering determine whether it's a metadata inconsistency in the Architect backend.

    Interested to hear what you find-this is an unusual one.



    ------------------------------
    Cesar Padilla
    INDRA COLOMBIA
    ------------------------------

    Original Message


Related Content