Scheduled Invalidation

Control the expiration of cached objects.

How it works

This behavior controls when the cached content that satisfies the rule's match criteria expires. You can configure expiration as a one-time event or at a repeating interval.
In addition to periodic cache flushes, you can use this behavior to minimize potential conflicts when related objects expire at different times.

🚧

Scheduled invalidations can significantly increase origin servers' load when the matching content expires simultaneously across all the edge servers. As a best practice, schedule expirations during periods of lowest traffic.

Features and options

Field

What it does

Sub-options

Start Date

Specifies the date and time when matching cached content is to expire. You can select the date, time and time zone.

Enable Repetition

When enabled, invalidation recurs as indicated in the Repeat Interval field, beginning at the time indicated in the Start Date field.

Repeat Interval

With Enable Repetition set to On, specifies how often to invalidate content, starting from the Start Date time. You can specify a set number of seconds, minutes, hours or days. For example, an expiration set to midnight and an interval of 86400 seconds invalidates content once a day. Repeat intervals of less than 5 minutes are not allowed for NetStorage origins.

Refresh Method

Specifies how to invalidate the content.

  • **Purge only if modified**. Re-caches the content only if the origin has fresher content.
  • **Purge**. Re-caches content regardless of its freshness, potentially creating more traffic at the origin.

Did this page help you?