As of maybe 2 hours ago, once I push a version of a container to an environment, that environment gets stuck on that version. The version list updates, but the actual container file downloaded from the CDN doesn’t get updated.
I’ve tried creating new environments, and they all get stuck on whatever I push them to. I even tried creating a whole new container. I’ve also tried downloading them in incognito mode, and even in a different browser. The CDN still serves up the same file.
Steps to reproduce:
- publish version 1.1 to environment envone
- Observe envone version in the list is 1.1 (expected)
- download envone container file (https://cdn.matomo.cloud/someinstance.matomo.cloud/container_abc_envone_def.js)
- Observe envone’s container file contents are for version 1.1 (expected)
- publish version 1.2 to envone
- Observe envone version in the list 1.2 (expected)
- download envone’s container file (https://cdn.matomo.cloud/someinstance.matomo.cloud/container_abc_envone_def.js)
- Observe envone’s container file contents are still version 1.1 (not expected, should be 1.2)
- publish version 1.2 to environment envtwo
- Observe envtwo version in the list is 1.2 (expected)
- download envtwo container file (https://cdn.matomo.cloud/someinstance.matomo.cloud/container_abc_envtwo_ghi.js)
- Observe envtwo container file contents are for version 1.2 (expected)
- publish version 1.3 to envtwo
- Observe envtwo version in the list 1.3 (expected)
- download envtwo’s container file (https://cdn.matomo.cloud/someinstance.matomo.cloud/container_abc_envtwo_ghi.js)
- Observe envtwo’s container file contents are still version 1.2 (not expected, should be 1.3)
Is the CDN employing some new cache rules or something?