This is incredibly frustrating. I maintain over fifty Architect flows for our organization. We have a weekly process where our marketing team updates a specific User Prompt with a new promotional message. They upload the new .wav file using the exact same prompt name and ID. However, when callers dial in, some callers hear the new promotion, while others still hear the old message from last week! This inconsistency can last for up to 24 hours. Does the Genesys Cloud Edge device cache audio prompts locally, and if so, is there an API endpoint or an Architect action to force the Edge to flush its prompt cache immediately after an update?
As a fellow flow designer, I feel your pain. Yes, the Edge devices aggressively cache audio prompts to reduce bandwidth and latency. When you upload a new audio file to an existing prompt resource, the platform does send a cache invalidation signal to the Edges, but in a large deployment with many Edges, this synchronization can sometimes lag or fail silently. There is no public API to force a cache flush on the Edges.
Hey there! I am a big fan of the audio APIs! to follow up on the earlier suggestion, a much safer pattern for frequently changing audio is to stop overwriting the same prompt file. Instead, create a Data Table in Genesys Cloud. Put the promotional prompt name in the table. When marketing has a new promo, they upload a brand new prompt (e.g., Promo_Week42) and just update the string in the Data Table. Your Architect flow reads the table at runtime and plays whatever prompt name is listed. Because the flow is requesting a new prompt name, the Edge is forced to fetch it immediately. No caching issues ever!
I look at the fallout from these issues on our executive dashboards. 's workaround is functionally correct, but it creates a massive garbage collection problem. If you upload a new prompt every week, your prompt library will have hundreds of orphaned audio files after a year. This makes auditing and reporting on prompt usage a nightmare. If the platform’s native cache invalidation is broken, Genesys Support needs to fix it rather than us building messy workarounds that pollute the tenant storage.