Thanks for the question. This appears to be the same issue you reported previously here, where Ashley provided the recommended approach:
- use
catalog.version.updated - re-fetch the affected objects
- compare their
versionvalues
Catalog reads can be briefly eventually consistent, but if stale values remain for more than a few seconds, compare a direct curl response with your website at the same moment to check for application, CDN, framework, or HTTP caching. If the direct API response itself remains stale, please provide the object ID, timestamps, endpoint, returned versions, and sanitized responses so we can investigate.
Hope this helps!