The Dispatcher may stop updating cache files if the request to the page in question contains query string parameters because such requests are typically not cacheable. Additionally, if the request has authorization headers and dispatcher.any does not contain the allowAuthorized property, the Dispatcher will not cache the response for security reasons. Another reason could be that the Dispatcher Flush agent is disabled on the publish instance, preventing the cache from being manually cleared and updated. The requirement that the request URI should always start with /content is irrelevant to the Dispatcher updating cache files.