XM Cloud Known Issues and Gotchas (2026.1)

Issue 1: JSS Middleware 504 Timeout

Symptom: Deploying JSS Next.js apps to Vercel results in 504 middleware timeout errors, especially with many URL query parameters.

Root cause: JSS SDK 22.2.0 and earlier had inefficient middleware processing.

Fix: Upgrade to JSS SDK 22.6.0 or newer. This issue is resolved in recent versions.

Impact: High — can cause production outages if not addressed.

Issue 2: JSS + Next.js 15 Peer Dependency Conflict

Symptom: npm install @sitecore-jss/sitecore-jss-nextjs fails with peer dependency errors when using Next.js 15.

Root cause: JSS SDK 22.10 peer dependency declaration still specifies Next.js 14.x, despite supporting Next.js 15 functionally.

Workaround: Install with --legacy-peer-deps flag:

npm install @sitecore-jss/sitecore-jss-nextjs --legacy-peer-deps

Status: Open as of February 2026. Functional workaround available.

Impact: Medium — CI/CD pipelines must account for this flag.

Issue 3: Experience Edge Rate Limits

Symptom: GraphQL queries return 429 (Too Many Requests) errors under load.

Root cause: Experience Edge enforces rate limits on GraphQL API requests. While specific limits are not publicly documented, high-traffic sites using SSR commonly encounter these limits.

Workaround:

1. Use SSG instead of SSR (dramatically reduces API calls)
2. Implement frontend caching
3. Contact Sitecore support to increase rate limits for your environment

Impact: Medium — easily avoided with proper architecture (SSG).

Issue 4: No Server-Side Search

Symptom: You expect built-in search like Sitecore XP’s Solr, but there is none.

Root cause: Architectural decision — XM Cloud doesn’t include search.

Workaround: Use Sitecore Search (separate license), Algolia, Elasticsearch, or build custom search by indexing Experience Edge data.

Impact: Medium — plan for search solution during architecture phase.

Issue 5: xDB Analytics Don’t Migrate

Symptom: Migrating from Sitecore XP, you expect to bring xDB analytics history. It doesn’t migrate.

Root cause: xDB doesn’t exist in XM Cloud architecture. Analytics are handled by Sitecore CDP (separate product).

Workaround: Export xDB data to a data warehouse before migration if historical analytics are critical.

Impact: High for organizations relying on historical analytics data.