IIIF Presentation uses Protagonist named-queries to generate content-resources for assets on a manifest. If there are frequent changes to a manifest we could be making a number of calls for named-queries in a short space of time. We could run into issues if we are served a cached/stale version of a manifest as it could be rendering out of date assets.

We are filtering by batch-id to images can't be added but they could change if:

• A failing image is successfully reingested
• A successful image has been reingested and failed
• An origin changes and the source image is a different size
• A policy, e.g. thumbnail policy, changes meaning different sizes are available.

Some of these are more likely than others but to avoid potential issues we should append some sort of cache-busting query parameter to the request as the Protagonist cache varies by query-param. This should be random, suggested ?cacheBust={DateTime.UtcNow.Ticks}.