Genesys Casual

I wasn't sure exactly where to ask this question, so I thought I'd start it here.

I've noticed that when we have a request to update audio prompts in GenCloud for an Inbound call flow, after the prompt(s) are updated with a new audio file, the flow has to be opened and then republished to pick up the change to the related prompts that the flow consumes.  This wasn't the behavior when working with the older PureConnect platform.  It "feels" like audio prompts are cached in memory and republishing the flow, causes all prompts for that flow to be refreshed.  I also didn't see this mentioned in any of the training material, although I could have missed it along the way.

The first time we had a request like this, we updated our prompts but did not republish the flow.  The next day, we got a call from our customer that the system was still playing the older version of the prompts, like it wasn't updated.  We navigated into the Prompts section, and were able to play the new prompt.  As a troubleshooting step, we decided to just republish the flow and it worked.  Now going forward, we just republish the flow as a standard process when we have similar activity.

My question is - has anyone else experienced this or is this unique to just us?

Hey Michael,

That's how it works for us as well. Whether or not that's the intention and the reason behind it, I'm not positive, but it is a part of our process when we update prompts. I'm not sure if there is anyway to change that either.

------------------------------
Tristen Schwarzenberger
IT Engineer
GCP
------------------------------