Limitations and restrictions of Experience Edge

For performance reasons, a single query can return a maximum of 1,000 entities. To fetch more, use pagination.

The Experience Edge Connector publishes a static snapshot of the Layout Service output for an item at the time of publishing. This means that:

The LinkManager encodes spaces into dashes. So, if two items under the same parent differ only by a space or a dash (like Test Item and Test-Item), they will get the same identifier. This means that only one of them will be available on Edge after publishing.

Sitecore tracking/analytics do not reflect Experience Edge API calls.

Experience Edge does not enforce security constraints on Sitecore content. You must apply publishing restrictions to avoid publishing content that you do not want to be publicly accessible.

Sitecore language fallback rules are applied at publish time and can only be enabled/disabled on an instance and not on individual sites. If you change the language fallback configuration, you must republish the affected items.

Because templates are not stored as items, you can't directly fetch their data using an item query. Attempting to do so will return null values. However, you can fetch data for another type of published item that includes information about its template, as shown in the following example:

The value an item inherits through clones and standard values is resolved at publish time. A change to a clone source or standard value requires republishing dependent items.

Experience Edge only utilizes a single content scope for the whole tenant. Security tokens, query cache clearing, and webhooks cannot be limited by site.

The maximum size for Media items is 50MB.

Experience Edge supports up to 1,000 sites per tenant.

Experience Edge supports up to 9990 redirects.

Experience Edge doesn't support virtual folders.

Experience Edge doesn't support aliases.

When using a culture (locale) in an Edge query, the value is always case-sensitive. For example, if the culture is it-IT, a query of it-it returns null.

The combined number of paths supplied to the includedPaths and excludedPaths arguments in the siteInfo.routes field is limited to 100. This limit applies to the number of path strings you provide, not the number of items under those paths. For example, the following argument is counted as 4 paths, regardless of the number of entries each path has.

{
  "includedPaths": ["/products", "/services"],
  "excludedPaths": ["/blog", "/find-trials/study"]
}

You can use the following sample query to display all available routes for a site in a specific language to ensure you're below the limit:

{
  "siteName": "yoursitename",
  "language": "en"
}

query ($siteName: String!, $language: String!) {
  site {
    siteInfo(site: $siteName) {
      routes(language: $language) {
        total
        results {
          route {
            id
          }
          routePath
        }
        pageInfo {
          endCursor
          hasNext
        }
      }
    }
  }
}

The Experience Edge GraphQL endpoint is rate-limited. If you are building a very large website, you must enable retries for requests to the Experience Edge GraphQL endpoint to complete builds. If you exceed the limit, Edge returns a 429 response. The following rate limits apply, and are visible in the header response:

The mirrored schema might return inconsistent results when filtering or sorting by item text fields due to differing tokenization.

Layout data in Experience Edge only supports the Default device layer in item presentation.

Media URLs in Experience Edge are case-sensitive. For example, to reference an item in the Images\Banners folder, where the folder names are capitalized, use the following:

https://edge.sitecorecloud.io/mainwebsite/media/Images/Banners/promo-banner.jpg

Experience Edge doesn't support multiple site definitions pointing to the same start item.

Using "*" has target hostname causes errors during publishing.

Persisted queries aren't supported.

Due to a known issue in the Experience Edge GraphQL schema, you must not mix literal and variable notation in your query input. If you use any variables in your GraphQL query, you must replace all literals with variables.

query MyQuery($hasLayout: String!, $parent: String!) {
  search(
    where: {
      AND: [
        { name: "_hasLayout", value: $hasLayout }
        { name: "_parent", value: $parent }
      ]
    }
  ) {
    total
  }
}

query MyQuery($parent: String!) {
  search(
    where: {
      AND: [
        { name: "_hasLayout", value: "true" }
        { name: "_parent", value: $parent }
      ]
    }
  ) {
    total
  }
}