Genesys Cloud - Main

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Architect flows and organization default TTS/Voice changes: how to handle this at scale?

  • 1.  Architect flows and organization default TTS/Voice changes: how to handle this at scale?

    Posted 6 hours ago
    Hi everyone,
     
    After changes to the organization default TTS engine/default voice and changing the default voice for a supported language, existing Architect flows show this message:
     
    "This flow was saved with language-xxxxxxxxx as the default voice for the selected engine. If the flow is edited, the voice for this language will be updated to the current default voice."
     
    This seems to indicate that existing published flows do not automatically pick up the new default voice. Instead, each flow needs to be edited, saved, and published again so the supported language configuration is updated to the current default voice.
     
    For customers with many Architect flows, how are you handling this at scale?
    On the Ideas Portal, the closest item I found was this idea: https://genesyscloud.ideas.aha.io/ideas/SSA-I-248

    #API/Integrations
    #Implementation
    #Routing(ACD/IVR)

    ------------------------------
    Att,
    Breno Canyggia Ferreira Marreco
    ------------------------------


  • 2.  RE: Architect flows and organization default TTS/Voice changes: how to handle this at scale?

    Posted 3 hours ago
    Hi Breno,
     
    This is a known behavior in Architect, and currently there isn't a built-in way to bulk update or republish flows when TTS voice settings change.
     
    When a flow is published, Architect stores the configured TTS engine and voice as a snapshot. This ensures published flows remain consistent, even if the organization's default voice settings are updated later. As a result, existing flows must be republished before they'll pick up any new default TTS settings.
     
    Today, the supported option is to open, save, and republish each flow individually. While this doesn't scale well for larger deployments, you can automate much of the process using the Genesys Cloud Platform API. For example, you can retrieve your flows using the `GET /api/v2/flows` endpoint and then programmatically republish them using `POST /api/v2/flows/actions/publish`, allowing you to script the process rather than updating each flow manually through the UI.
     
    The Ideas Portal request you referenced highlights this exact pain point, and there's also a related idea, SSA-I-363 (Architect - Mass Publish All Flows That Use a Common Module), which is currently in Future Consideration.
     
    While there isn't a native bulk publish capability today, this is another area where the community may have developed automation or scripting approaches. I'd love to hear how others are handling large-scale TTS updates in their environments.

    Cheers, 



    ------------------------------
    Cameron
    Online Community Manager/Moderator
    ------------------------------



  • 3.  RE: Architect flows and organization default TTS/Voice changes: how to handle this at scale?

    Posted 2 hours ago
    Edited by Breno Canyggia Ferreira Marreco 2 hours ago

    Hi Cameron, thanks for the confirmation.
    As for Commons, I’ve pretty much given up on the struggle. Haha. But I was hoping for a better outcome with TTS.



    ------------------------------
    Att,
    Breno Canyggia Ferreira Marreco
    ------------------------------

    Original Message


Related Content