Skip to main content

How to Determine the Expected Total Arc XP Cache TTL

Summary

The time that passes between updating a page or content in Arc XP and when this change appears on the live site will vary. The time depends on the cache configuration, where the page or content appears on your site, and what content source(s) are involved in rendering that content.

This procedure will allow you to determine the maximum expected time for a change to appear on your site.

Procedure

The total maximum expected time for changes to content is the sum of the Akamai True TTL, and the Content Source TTL.

Determine the Akamai True TTL

The following procedure may vary slightly depending on the browser used.

  1. Open the target page or content in the browser.

  2. Open Inspector, in the browser.

  3. Select Network

  4. Refresh the page.

  5. If desired, filter for "Doc" and select the document for the requested page. This will usually be the first in the list.

  6. Scroll down to "Response headers"

  7. Locate the header Akamai-True-TTL

Determine the Content Source TTL

  • Content source cache is generally set to 5 minutes (300 seconds) for content sources provided by Arc XP.

  • Custom content sources may be configured with any TTL.

  • The TTL is generally configured in the content source, .js file but also may be configured as an environment variable referenced from this file.

Troubleshooting Notes

  • The sum of the Akamai True TTL and the Content Source TTL represents the maximum time expected for changes to appear on the site.

  • In some circumstances, changes may appear sooner, however, updates occurring within the sum of these two TTL's is normal. 

  • The above information applies to changes. New content that is not cached, and which is appearing at a new URL should normally appear much sooner than these configured TTL's.

More Information

In this section: