Personalization no longer requires components to be marked as compatible to be swapped with each other in a page variant. This gives authors more flexibility when configuring personalized experiences and reduces configuration overhead for developers.
This release of Page builder also includes the following fixes:
Container components that are hidden using personalization no longer cause nested components to appear as broken in Page builder.
Authors can now remove or repair components that were inside a broken container directly in Page builder, avoiding the need for manual cleanup in Presentation Details.
The Open in Content editor button is now correctly shown in the right-hand content tab wherever applicable, allowing authors to jump directly from Page builder to Content Editor.
Page translation now correctly includes content coming from associated partial designs, ensuring translated pages are complete.
In the Page content context panel, the fallback value labels now correctly show the language that provides the fallback value, helping editors understand content origin without leaving the builder.
Page builder now fully respects the workflow command Suppress comment configured in Content Editor, so comment prompts only appear when they are expected.
In Rich Text fields, adjacent <ul></ul> blocks as now kept separate <ul> blocks instead of merged, keeping list structure and spacing as authored.
Page builder now sets the dam-content-type metadata correctly when authors add Content Hub assets, ensuring consistent and accurate asset metadata.
With Content mode, you can:
Create pages, folders, and content items quickly using guided insert options that show only valid templates.
Search for content items in a flat, paginated list that scales to large content structures and opens items directly in full view.
Work more efficiently when you know what you want to create or find, without browsing through multiple tree levels.
Search within an item to locate a specific field and edit it in a distraction-free, full-screen field editor.
Content mode is designed to help authors move faster and manage content at scale with fewer clicks and less context switching.
]]>Improvement to synchronization of CMP entities
In the integrated Sitecore Connect for Content Hub connector, the synchronization of CMP entities has been made more resilient. The improvement has been achieved by altering the management of the client’s lifecycle and by adding additional retry and throttling handling for common network transient errors.
Reduced memory consumption by interning strings and IDs from resource files
Strings and IDs from Item as Resource files have been added to interned dictionaries to reduce duplicate strings and IDs, including those read from SQL storage. This improvement results in reduced memory consumption.
Enhancement to logging in the MemoryLimitCachePurgeAgent task
The logging level in SitecoreAI's MemoryLimitCachePurgeAgent scheduled task has been increased from DEBUG to INFO. This improvement makes it easier to detect potential cache size issues.
Tracking of Solr behavior
Functionality has been added to allow further investigation of Solr performance and behavior issues on the SitecoreAI backend.
The latest release of the SitecoreAI base image 1.7.5 includes the following resolved issues:
Fixed a defect in the Content Editor where a NullReferenceException was being thrown when an item with a Multiroot Treelist field had a datasource that does not contain a tokenized query.
Resolved incorrect logging of publishing errors when no entities had failed. Now errors are only logged when failures occur.
Added a deadline timeout to every unary gRPC call to prevent potential stalling of publishing process.
Ensured item statistics are sent to Publishing API even when no items are published.
Fixed intermittent race condition in publishing process that caused NullReferenceException by improving thread safety checks.
Resolved issue where validation errors for datasource items in the Page builder were not displaying the field name when using language fallback.
Fixed defect where StandardValues field value was not being updated when the serialization push command is used for the first time.
Sitecore PowerShell Extensions (SPE) 8.0 is being upgraded to 8.0, and any PowerShell script that is not compatible with the later version may stop functioning after the upgrade.
The SPE upgrade has also resulted in the SitecoreAI base image release version being increased to 1.7.5.
Release timeline for SPE update:
14 April 2026 – SitecoreAI base image released and automatic update for non‑production environments.
22 April 2026 – Automatic update for production environments.
Optional early update for production
Customers who wish to benefit from the update earlier may manually update their production CM instance by performing a deployment activity as soon as the new base image is released.
Script validation recommendation
There are no changes to the planned feature set, but we strongly recommend validating your existing scripts to ensure compatibility with SPE 8.0. You can use the following guide to verify and adjust your scripts before the automatic rollout:
How-to's - How to validate PowerShell scripts for compatibility with Sitecore PowerShell Extensions…
More details on the deployment process are available here: https://doc.sitecore.com/sai/en/developers/sitecoreai/sitecoreai.html
Added the ability to rename assigned content items directly in the Page builder UI so authors can keep content organized without switching to Content Editor.
Added a direct link to the SitecoreAI changelog in the Help menu so users can quickly review recent updates without leaving the Page builder.
Added an editing option to the Manage Items view for Link lists. Authors can now open items directly in Explorer or Content Editor.
Page creation from large branch templates is now faster.
The latest release of Page builder also includes fixes for the following issues:
The Create support ticket action is now visible only to organization Admins and Owners.
Opening the Add media dialog could be slow in large media libraries. The media library now defaults to the current site media root folder when no source field is defined, which improves performance.
SitecoreAI introduces Profiles, a new addition to the Audience and insights capability that lets you explore and act on site visitor data directly from within SitecoreAI.
Profiles list - view your most recent site visitors, and filter or search for the profile you're interested in.
Profile details - see a rich snapshot of each site visitor, including a session heatmap, daily device usage, top affinities, a world map of session locations, and more session and event details.
Profiles make it easier to turn the visitor data collected through identity resolution and affinities into actionable insights, helping marketing analysts and administrators understand individual customer journeys and make informed personalization decisions.
]]>sitecore-jss-nextjs. It also introduces breaking changes, including upgrades to Next.js 16 and Node.js 24, plus an update to React placeholder suspense behavior.Review the relevant upgrade guides for comprehensive instructions on updating your apps:
]]>Reduced memory consumption and cache footprint through use of interning
The repeated use of identical IDs within AccessResultCacheKey.longIdIndexParameters values, such as the Sitecore Root ID, was causing significant memory overhead and inflated cache sizes. By adding support for interning repeated values in longIdIndexParameters, memory consumption and overall cache footprint have been reduced.
Improved performance of CMP relation processors in the Content Hub import pipeline
The integrated Sitecore Connect for Content Hub connector now synchronizes CMP entities (content items managed in Content Hub, including their associated metadata and relationships) more efficiently. This improvement optimizes relation data fetching through parallelization and prevents repeated retrieval of the same related entity information across pipeline processors, reducing latency during CMP imports.
Enhanced logging for cache clearing operations
Logging has been improved to provide full stack traces whenever all caches are cleared. This enhancement makes it significantly easier to diagnose issues related to cache invalidation and provides deeper visibility during troubleshooting.
Addition of site context properties to Delivery API SiteInfo graph type
Added all site context properties to the attributes collection of the GraphQL SiteInfo graph type in the Delivery API. This change means that when a user adds a custom site property to a site definition item's 'other properties' field in the Content Editor, it is exposed on the Delivery API and can be fetched by a GraphQL query
The latest release of the SitecoreAI base image 1.6.1483 includes the following resolved issues:
Reverting the change that fixed the issue where publishing a partial design datasource triggered an unnecessary publish of all pages using this partial design when Publishing V2 is enabled. An edge case was identified impacting certain customers that must be resolved before this becomes the default behavior. A temporary setting was introduced for customers unaffected by the edge case who may wish to opt in to this behavior. This setting should be applied only on recommendation from Sitecore as it will be removed again in the future when the new default behavior is permanently applied.
Removed unnecessary processing of templates and standard values in order to reduce time it takes to save a content item that is referenced by a large number of other items.
Datasource workflow actions now work correctly when a content item references itself as a datasource of a rendering.
Prevented unintended translation of partial design datasources each time a page is translated.
Fixed a defect where site standard values could overwrite the global template's standard values, causing fields to resolve to an incorrect value.
Addressed an issue where sitemap refresh jobs could block the Sitecore job queue.
Corrected an issue where content item versions that had previously been deleted were unintentionally recreated after migration with the XMM Migration tool.
Resolved a defect in the Content Editor where the workset state was not being reset to the initial state when a new version is created and the RequireLockBeforeEditing setting is set to false.
Incremental publish now correctly includes and publishes language fallback content across all configured languages.
Corrected an issue where HTTP 524 errors were not being retried during publishing.
Restarting a CM instance now correctly updates job states in the Publishing jobs UI.
Fixed an issue in the publishing process where the same entity could be sent for publishing multiple times.
Resolved a defect in the Page builder where source queries did not work if there were spaces in the template name
Fixed the logic of splitting the Solr update operations into batches, resolving an issue where an excessively large batch could be created and sent to Solr, causing some data to be missing from the search index.
We’ve updated several Marketer MCP tool names to meet MCP client limits (60-character max). This is a breaking change and any existing references to previous tool names will no longer work and must be updated.
Previously, longer names could be filtered out or rejected by MCP clients like Cursor, which could cause errors when referencing those tool names directly in prompts.
These updates ensure tools remain visible and can be reliably called by name across MCP environments.
What changed
Tool names were shortened while keeping their original meaning. Examples include:
Previous name | New name |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Required action
Update all prompts, scripts, and integrations that reference these tools by name to use the new tool names.
Replace any hardcoded references to previous tool names.
No update required if tool names are not referenced explicitly.
Impact
Existing integrations or setups that reference these tools by their old names will fail until updated.
Prevents tools from being hidden due to name length limits.
Avoids errors when referencing tool names directly in prompts.
Ensures consistent tool calling across MCP clients.
Note: These tool name changes do not affect actual tool behavior.
We’ve also updated the Marketer MCP server URL to: https://marketer.sitecorecloud.io/mcp/marketer-mcp-prod. The previous URL: https://edge-platform.sitecorecloud.io/mcp/marketer-mcp-prod is still supported but is being deprecated.
There is no required action. Existing integrations using the previous URL will continue to work, but we recommend using the updated URL for new configurations.
Agents are structured to work with context, items, and tools as part of your day-to-day workflows.
Work with items - agents can run on items like SitecoreAI pages, briefs, artifacts, and CSV files. Agents process selected items across parameters (like languages) to generate outputs for each combination. They also enable content at scale from structured inputs, such as accounts in a CSV.
Use built-in tools and features - chat interfaces across Agentic studio let you set context, skills, MCPs, and tools for each run, giving you more control over how the agent behaves.
You can define and configure agents and workflows to match your needs.
Create standard agents - define standard agents with instructions, tools, skills, context, and output formats for a flexible, chat-style experience.
Add new workflow actions - create workflow agents that support invoking standard agents, calling external APIs, and invoking Agent API tools.
Manage skills and tools - a Settings page brings together tools, skills, schemas, templates, user management, and job tracking.
Use agent skills - apply built-in agent skills such as campaign planning, competitive analysis, and CSV/text processing, or create your own.
Reuse schemas and templates - JSON schemas and HTML templates are managed globally by admins and reused across agents.
Test workflows - agent workflows can be tested with step-by-step visibility, including timing and error reporting.
Agents can be used across larger workflows and datasets.
Create a space - create a space for bulk updates, content generation, or custom workflows. Select multiple agents, define items, and set parameters in one place.
Chain agents together - run any agents in sequence (for example, research, content generation, then translation) within a single space. You can share context and run agents directly on existing artifacts.
Update space status - change the status to reflect progress, whether action is needed, and what comes next.
Trace and group results - track artifacts across steps and group them by agent or item.
Simplified experience - running agents, flows, and spaces follows a consistent setup with inputs, parameters, context, items, or files.
Simplified space layout and views - a space now includes a main area for artifacts with Classic, Chat, and Canvas views, and a right-side pane for agents and instructions.
Markdown support: a foundation for what's next
The documentation platform now uses a Markdown-based content model internally. This provides a more flexible and scalable foundation for documentation, and establishes the groundwork for Markdown export and direct editing capabilities.
New and improved viewing options
Reading and navigating documentation is now easier and more customizable than ever:
Collapsible sidebar panels for a cleaner navigation experience
Focus mode to reduce visual distractions
Adjustable font sizes to tailor how you read
Full‑width article view for a more spacious, distraction‑free layout
A refreshed UI built on the latest version of Blok
The doc site interface has been fully updated using the newest Blok components, delivering a cleaner, more consistent, and more accessible experience across all documentation.