Cache Purging Scenarios

Contentstack purges cache of only the content that has been changed (published, unpublished, or deleted) and other related data (referenced content) from the Content Delivery Network. This purging takes place only on the specific locale and environment on which the cached content exists.

For instance, when you delete a referred child entry, Contentstack purges all the cached entries of that child content type (on concerned locale and environment) and the cached entries of all parent content types (on concerned locale and environment) that refer to the child entry. The purging mechanism moves up the reference chain.

Contentstack purges cached data only when an API request attempts to publish, unpublish, or delete content. Such API requests comprise the name of the publishing environment as a query parameter.

Additional Resource: Learn how to scan cache headers returned in the response of an API request to understand where your content is being delivered from.

Let us look at a few scenarios to understand how Contentstack purges only relevant cached content from the specific locale and environment.

Consider a scenario where you have a “News Articles” content type with entries that contain details of specific news articles. Each article also comprises appropriate images related to the specific news item. The list of articles is provided below:

  • News article 1
  • News article 2
  • News article 3

Each article also has references to a specific author bio from the “Author Details” content type. This content type contains bios for all authors that contribute to news articles. Apart from the biography, each entry of the “Author Details” content type also includes an asset that represents the profile picture of a specific author.

The website’s home page also contains a section that displays recently added articles. The “Home Page” content type has a “Reference” field that refers to the “News Articles” content type to pick up newly added articles regularly. The content manager has also added an asset to the home page, which represents the company logo.

Since the website is multilingual, the company publishes the above articles in the following languages:

  • English (United States)
  • French (France)
  • German (Germany)

The articles and the home page have been published on all the following environments to reflect the same changes everywhere:

  • Development
  • Staging
  • Production

The CDN stores cached copies of all these articles, the author bios, the home page, and all the referred assets once they are published.

Edit and Publish the Home Page

Now, suppose if the content manager edits the company description in the “Home Page” content type. Once done, the author publishes the “English (United States)” version of the content to all the three available locales and on the “Production” environment.

The following cached data will be purged:

  • “English (United States)” version of the “Home Page” entry on “Production” environment
  • “French (France)” version of the “Home Page” entry on “Production” environment
  • “German (Germany)” version of the “Home Page” entry on “Production” environment

Note: We do not purge cached assets and their download URLs when an entry is published or unpublished.

Edit and Publish the Company Logo

Now, suppose if the content manager replaces the existing company logo in the “Home Page” content type with the latest version. Once done, the content manager publishes the “English (United States)” version of the company logo to all the three available locales and on the “Staging” and “Production” environment.

The following cached data will be purged:

  • “English (United States)” version of the “Home Page” entry, along with all assets referred with the entry, on “Staging” and “Production” environments
  • “French (France)” version of the “Home Page” entry, along with all assets referred with the entry, on “Staging” and “Production” environments
  • “German (Germany)” version of the “Home Page” entry, along with all assets referred with the entry, on “Staging” and “Production” environments

Note: We do not purge cache of the download URLs of the assets when an asset is published or unpublished.

Edit and Publish a News Article Entry

Now, suppose a content manager updates any article and publishes the changes to the “German (Germany)” locale and the “Development” environment.

The following cached data will be purged:

  • All entries of the “News Articles” content type present in “German (Germany)” and published to “Development”
  • All entries of the “Home Page” content type present in “German (Germany)” and published to “Development”

Note: We do not purge cached assets and their download URLs when an entry is published or unpublished.

Delete an Author Biography Entry

Now, suppose if the content manager deletes an author bio entry from the “Author Details” content type. This author’s bio was localized in “French (France)” and published to the “Production” environment.

The following cached data will be purged:

  • All entries of the “Author Details” content type present in “French (France)” and published to “Production”
  • All entries of the “News Articles” content type present in “French (France)” and published to “Production”
  • All entries of the “Home Page” content type present in “French (France)” and published to “Production”

Note: We do not purge cached assets and their download URLs when an entry is published or unpublished.

Delete an Author Profile Pic

Suppose an author’s profile pic was being referred in all the three locales: “English (United States)”, “French (France)”, and “German (Germany)”, and published to the “Production” environment. For this example, we consider the following scenarios:

  • Content manager deletes the author profile pic from the asset manager of the stack
  • Content manager detaches the author profile pic from an entry of the “Author Details” content type

In both the above-mentioned scenarios, the following cached data will be purged:

  • All entries of the “Author Details” content type present in “English (United States)”, “French (France)”, and “German (Germany)”, along with all assets referred within the entries, and published to “Production”
  • All entries of the “News articles” content type present in “English (United States)”, “French (France)”, and “German (Germany)”, along with all assets referred within the entries, and published to “Production”
  • All entries of the “Home Page” content type present in “English (United States)”, “French (France)”, and “German (Germany)”, along with all assets referred within the entries, and published to “Production”

Note: We do not purge cache of the download URLs of the assets when an asset is published or unpublished.

Was this article helpful?

Thanks for your feedbackSmile-icon

On This Page

top-arrow