When you use Version Management, you can edit various configuration settings, such as WAF custom rules and Cache settings.
Generally, you are allowed to edit all zone-level configurations except for the following:
Version Management does not currently support or have limited support for the following products or features:
- Some API Shield settings are not cloned when a new zone version is created.
- Customers are allowed to opt-in to remove the UI block that prevents enabling Version Management.
Authenticated Origin Pull
- Authenticated Origin Pull does not work with Zone Versioning.
- Accessing your domain from an allowlisted IP returns a Cloudflare 520 error.
- Cache settings are versioned, but cache keys are not.
- Caching a new URL on staging would cache it for production as well.
- Purging cache on staging would purge it on production too.
- Promoting a new version to production would wipe all exiting cache.
Cache Rules when used with Cloudflare Images
- Image Resizing does not work with the
additional_cacheable_ports Cache Rule setting and Zone Versioning.
- If you use
additional_cacheable_ports with Image Resizing, the image will be resized every time it is requested and will result in low performance.
Workers Cache API
- Workers Cache API does not work with Version Management.
- If you use the Workers Cache API with Zone Versioning, you might encounter unexpected caching behaviours.
- Regardless of the version deployed to production, traffic in China will always target the root zone.
- Other incompatibility issues with Access and ICP licenses.
- Zone Version Management does not currently expose a public API.
- Customers can only use Version Management through the Cloudflare dashboard.
- Domain-scoped Roles apply only to your root zone.
- Once a new version is created, these roles do not copy over and they lose access to versions.
Network Error Logging
- Security Insights are not shown when Zone Versioning is enabled and the first version is deployed to production.
- Zone Version Management does not currently support Terraform.
- Customers should either use Terraform or Version Management.
WAF Attack Score
- Waiting Room users active on the site may be placed back in the queue.
- Waiting Room users in the queue may lose their place in line.
- Traffic may exceed limits.
- If a version has a Worker route, it might disappear when a Worker is deployed via Wrangler.
- If two versions have the same custom domains, the Worker might randomly choose between them.