Recent searches
No recent searches
Zendesk API caching mechanism
Posted Jun 29, 2022
ticket update in the web UI can take ~50 seconds to come through the export API.
Unless I got something wrong, this is still not a workable solution for us.
If we're building workflows around your platform, seeing stale state causes a
lot of internal confusion, bug reports, and wasted time.
How can we resolve this stale data?
Can we turn up the resolution on the export API? (<1s) or add a search flag that
will guarantee we're not reading from cache?
0
2
2 comments
Greg Katechis
Hi Gal, I totally understand where you're coming from. While we don't expect 50s to be an average, we do have a caveat in a number of places that due to indexing, it can be up to a couple of minutes before search and export data will reflect the current state. We do have a cache expiration set to 60 seconds on our hosts (there is work being done to reduce this in the future), so if the issue is related to caching, trying the call again could point you to a host that does not have the cached state and therefore return more up-to-date results. Obviously, without anything in our APIs to indicate whether or not it's being returned from cache, it becomes almost impossible to do anything with that information from a programmatic standpoint.
To that end, we don't have anything in place that includes cache status, but I have reached out internally to see if that is something that we could add in the future. I'll let you know if I hear anything back on that request or if anyone from that team has a clever way of approaching this issue.
0
Jack
Greg Katechis
Are there any updates around that issue?
Requests page is cached for users and if they add new request they are not seeing it on requests page until few minutes and refreshing page. Can requests page be serve without caching? In my case it does not need to be indexed. Also I'm using custom theme
0