


Hi guys,
For pages and assets, once you publish(or republish) that content, the replication or distribution service will start the process of invalidating the dispatcher cache.
But how can I start the process of invalidating the response cache of a persistent query? It seems that publishing the content fragment does not do the trick.
(And I couldn't really find an answer in the documentation)
Any help is appreciated, thanks!
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @GuilhermeRios One option to invalidate response cache is browser cache duration in API Configuration screen.
Not sure if you already gone through below reference link:
Hi @GuilhermeRios One option to invalidate response cache is browser cache duration in API Configuration screen.
Not sure if you already gone through below reference link: