Content Sync provides different update priorities to fast-track important updates. Updates with a higher priority are processed earlier. When enabled, editors can select the priority of the update before pushing:
Access
The update priority feature is not included in all contracts- please reach out to us if you want access.
As this may incur additional costs, the priority feature must be enabled per space. Please reach out to us if you want to have it enabled on a second environment.
Priorities
Available update priorities in order are:
- Highly critical: This priority is not regularly available. It is enabled temporarily by us during critical publishing events when purchasing standby support.
- Updates are processed first.
- Updates ignore throttling.
- Updates are retried as fast as possible and then every 15-30 seconds on failure.
- We make another request to the site after the update completed to clear the entity cache and avoid stale caches during high-traffic publishing scenarios.
- Critical: Can be selected manually by editors to perform critical updates.
- Updates are processed after highly critical updates.
- Updates are retried as fast as possible and then every 30-60 seconds on failure.
- Important: When the priority feature is available on your account, this priority is assigned by default.
- Updates are processed after critical updates.
- Updates are retried as fast as possible and then every 60-120 seconds on failure.
- Regular: When the priority feature is not available on your account, this priority is assigned to all updates coming from a staging or production site.
- Updates are processed after important updates.
- Updates follow the regular retry interval.
- Low: When the priority feature is not available on your account, this priority is assigned to all updates coming from a development or local site.
- Updates are processed last.
- Updates follow the regular retry interval, but may be pushed back during high load.
Please note: Update priorities are non-blocking, so if e.g. you push one content with a high priority and one with a low priority, the high priority update is triggered first but the low priority update will also be triggered right after and may even finish earlier.