How-To: Troubleshoot Akamai Integration

Modified on Wed, 24 Jun at 7:40 AM

Schema App's Akamai integration bundle includes error message support. This suport document outlines how to access., interpret and action those messages.


Notes: This feature was launched in June 19 2026. If you downloaded the Schema App bundle before that date, follow steps 1.1 and 1.2 to ensure you are using an up to date version.


TABLE OF CONTENTS


How To: Review Network Header Responses

Navigate to the Network Tab and review response from the X-Schemaapp-Ew-Status to learn which troubleshooting action to take.


Step 1: Open Developer Tools and Emulate a Permitted Bot

  1. Navigate to the Developer Tools (CTRL + Shift + I or Right Click > Inspect).
  2. Ensure you are emulating a user agent that is permitted according to the Edge Worker Request Header → User-Agent settings. Review this support document for information on how to emulate a different user agent.
  3. Reload the page, proceed to Step 2.
  4. If you are blocked, the SchemaBot may need to be allowlisted. Review this support documentation for information on allowlisting SchemaBot.


Step 2: Navigate to Network Tab and Check the Document Headers

Schema App scripts run a response header with information about the status, URL, Account ID, and CDN Access messages

  1. Navigate to the Network tab
  2. Look for the Document, it will be first in the list of requests
  3. Scroll down the "Headers" tab to the X-Schemaapp-Ew-Status header
  4. Observe information about the following:
    1. reason
    2. lookup-url
    3. cdn-path
    4. cdn-mail
    5. cdn-highlight


Step 3: Interpret and Action the Reponse Messages

The responses in the header will guide next steps and troubleshooting actions. There are up to 6 relevant pieces of data


Status

This value will be either Bypass or Passthrough. Passthrough indicates a connection was made with our CDN for a specific account. Bypass indicates that no connection was made. The following values will provide further troubleshooting information.


Reason


This identifies if the request was successful and if not, why it failed.

Reasons include:

  1. no-markup
  2. missing-account-ID


Lookup-URL

This is the URL as represented in Schema App's systems. Check this to see if there are mismatches between this value and the live and/or canonical URLs.


CDN-Path

This is the Account ID and unique identifier for this URL in Schema App's systems. Check this to see if the Account ID is correct.


Note: Particular attention to whether it is the correct subAccount in the context of pre-PROD testing


CDN-Main

This is the status messsage received when the request communicated with Schema App's Editor cache


CDN-Highlight

This is the status messsage received when the request communicated with Schema App's Highlighter markup cache.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article