I am currently integrating our MuleSoft middleware with Genesys Cloud via Data Actions in Architect. We are seeing some strange ‘Caching’ behavior where the Architect flow receives a stale response from a Data Action even after we have updated the data in our back end system. Is there a default caching period for Data Action responses in the Architect engine, and is there a way to force a ‘Cache-Bust’ for critical real-time data lookups?
Hello Cla61! I am a consultant and I have seen this issue with many middleware integrations. Genesys Cloud Architect does not actually cache the results of a Data Action. Every time the ‘Call Data Action’ block is executed, a new request is sent to the platform. If you are seeing stale data, the caching is likely happening on your MuleSoft layer or in your corporate firewall. You should check your ‘Cache-Control’ headers being returned by MuleSoft.
Greetings! I am an admin for an Australian company and I love troubleshooting these API issues! To follow up on Emi24, please also check your ‘Correlation ID’. If you are reusing the same correlation ID for multiple requests, some intermediate proxies might be serving a cached response. Also, make sure you are not hitting a ‘Rate Limit’ on the MuleSoft side that is returning a cached 200 OK instead of an error. I have seen that happen during our peak volume tests!
I deal with the voice quality for our remote agents. Cla61, if you want a definitive way to ‘Cache-Bust’ the request, you can add a ‘Timestamp’ parameter to your Data Action input. In Architect, use the GetCurrentDateTimeUtc() function to pass a unique value in every request. This ensures that every call to MuleSoft is unique and cannot be cached by any intermediate network equipment. It is a simple and effective workaround!