DigitalOcean Spaces cache invalidation

We’re observing a problem with cache invalidation between DigitalOcean Spaces and Cloudflare. It seems like x-amzn-meta-max-age header is being honored in a sense that “age” response header doesn’t go over max-age. However, changes to the objects in Spaces bucket aren’t always picked up by CDN, last-modified timestamp does not match the latest object change time long after the max-age expiration. The problem is sporadic, max-age based invalidation sometimes works, sometimes doesn’t. If it doesn’t, the object gets stuck until manual invalidation. Explicit invalidation through DO API works. We started noticing this a couple of days ago. Is anyone else experiencing this?