2026 Optimizely Graph release notes

Follow this article to receive email notifications when new packages are available for Optimizely Graph. Product packages are found on the Optimizely NuGet server and and include updates to the following components:

• Optimizely.ContentGraph
• Graph Search UI
• Gateway
• Service Deployments

You can find prior versions of user guides and when functionality was released or deprecated at the following locations:

• Versioned user guides and release notes.
• Released functionality.
• Obsolete functionality.

Most recent releases

CMS to Graph Integration

April 21

Optimizely.ContentGraph.Cms 4.4.0

Enhancement

• Improved the resilience of the HttpClient configuration.

Bug fixes

• CMS-46635 – Fixed an issue where the Optimizely Graph full indexing job did not return error details when it failed to pull data about processing progress.
• CMS-47156 – Fixed an issue where LinkItem properties could generate incorrect or unclean language-specific URLs when linking to content across sites in Optimizely Graph.
• CMS-47939 – Fixed an issue where syncing Forms content containing List<ICondition> properties produced critical log errors during content type synchronization, even though indexing completed successfully.
• CMS-48801 – Fixed an issue where URLs stored in LinkItemCollection were not updated in Optimizely Graph when the referenced page was moved in the CMS tree.
• CMS-49458 – Fixed an issue where enabling a new language while Smooth Rebuild was active caused the language to be enabled only in the live slot instead of the rebuild slot.

January 20

Optimizely.ContentGraph.Cms 4.3.1

Bug fixes

• CMS-47482 – Fixed an issue where LinkItem properties returned from Optimizely Graph did not correctly encode special characters in the “Remaining URL” portion of the link.
• CMS-47995 – Fixed the content type synchronization issue that was occurring when content ID 1 was missing.

January 5

Optimizely.ContentGraph.Cms 4.3.0

Enhancement

• Added an in-memory queue system for event indexing to control the number of content items processed in parallel, preventing system overload during large content imports or publishing operations.

Bug fixes

• CMS-47223 – Fixed an issue where a full indexing job failed with a null reference exception when a content type included an integer property named "Id" and PreventFieldCollision was set to false. Additionally, validation has been added to prevent the use of reserved content type names such as SiteDefinition.
• CMS-47386 – Fixed an issue where the number of failed items in the delta indexing job output was incorrectly displayed twice (as 303303 instead of 303).
• CMS-47487 – Fixed an issue where content with a null name failed to sync to the graph.
• CMS-47011 – Fixed an issue where publishing a project would freeze the user interface until indexing was complete. Project publishing is now non-blocking, allowing users to continue working while indexing occurs asynchronously.

Graph Search UI

May 21

(Beta) Released Graph Search Management Portal, a UI for configuring Optimizely Graph search. Content editors and marketers can manage search behavior directly, without developer involvement for day-to-day tasks. The portal includes:

• Overview dashboard – Displays total query volume, click-through rate, and problematic queries (those with low or no click-through). Refreshes on demand and supports date-range filtering.
• Pinned Results – Promotes selected content to the top of search results for chosen queries. Create, edit, and delete rules in the portal. Changes take effect immediately. (Formerly Best Bets in Search & Navigation.)
• Synonyms – Expands query matching by defining term relationships. Supports two-way (equivalent) and one-way (directional) synonyms. Changes take effect within minutes. Access the portal from the Optimizely global navigation bar. 

Access requires Opti ID and Admin Center permissions for your Graph tenant. Pinned Results and Synonyms also require a one-time developer configuration. CMS integration is not yet available. Use the in-portal feedback link to share feedback during the beta. Learn more about the Optimizely Graph Search Management Portal.

Gateway

April 28

Gateway 3.27.0

Bug fixes

• CG-15978 – Fixed the issue where passing a full _id value (including language and status suffixes) into the ids argument of a GraphQL query returned no results. The ids argument now resolves full _id values correctly. 
• CG-16423 – Fixed the issue where cached responses for CMP documents were never invalidated, causing stale data to be served after updates. Cache purge now applies to all indexed documents regardless of publish status. 
• CG-16560 – Fixed the schema-sync error returned by Instance Manager when provisioning a new Content Graph instance for Structured Content tenants. 
• CG-16865 – Fixed the issue where image references inside experience compositions returned null DAM fields. 

March 25

Gateway 3.25.1

Bug fixes

• CG-15204 – Added the cg-include-deleted-only request header, which returns only deleted content from Graph. This lets developers build per-site wastebasket views without filtering deleted items out of mixed result sets.
• CG-13511 – Fixed the issue where the match operator returned an incomplete result set for media content types (ImageFile, VideoFile). Match queries now return all matching items, ranked by exact match, phrase match, full-word match, and partial match.
• CG-13946 – Fixed the issue where registering a new webhook through POST /api/webhooks returned a null id in the response. Newly registered webhooks now return a non-null ID.
• CG-15726 – Fixed the TypeError: This ReadableStream is disturbed exception returned by the _stream endpoint. Streamed bulk requests are no longer consumed before the underlying fetch is issued.
• CG-15931 – Fixed the issue where large GraphQL queries failed with query too complex. The threshold at which Graph switches to a wildcard _source includes has been lowered, so wide selection sets succeed more reliably.
• CG-16013 – Fixed the issue where pinned-result phrase matching was case-sensitive. Pinned phrases now match search terms regardless of case (Test and test are treated as equivalent).
• CG-16150 – Fixed the issue where the cg-include-deleted, cg-include-deleted-only, cg-include-hard-deleted, and cg-include-expired filters were silently ignored. These four filters are now sent as HTTP headers and applied as expected.
• CG-16360 – Fixed the issue where _metadata.content returned an empty string for media files indexed on CMS 13 sites. Extracted text content is now returned for newly indexed PDF, DOCX, and image assets.

February 2

Gateway 3.24.0

Bug fixes

• CG-6569 – Fixed the issue where faceting on ContentLink.Id returned a single empty bucket containing all content. Facets are now generated correctly for ContentLink.Id values. 
• CG-15716 – Fixed the issue where pinned items configured without a language returned no results when a specific locale was requested. Locale-agnostic pinned items are now returned for any requested locale, not just ALL. 
• CG-15740 – Fixed the 500 error returned by the GraphQL Gateway when a non-nullable field had no value. The gateway now returns a 400 response that identifies which field is missing a value. 
• CG-15802 – Fixed the issue where querying folders with _link (type: DEFAULT) returned an empty items array. _link(type: DEFAULT) now resolves linked content the same way _link (type: ITEMS) does. 

Service Deployment

February 2

Service Deployment 5.6.0

Enhancement

• Added Smooth Rebuild support to allow rebuilding Graph indexes with minimal disruption by keeping the existing index available while a new one is prepared. This approach helps reduce downtime and provides a safer way to apply schema or configuration changes to Graph indexes. Learn more about Smooth Rebuild.

Bug fixes

• CG-15806 – Fixed an issue where Smooth Rebuild was returning 0 results on subsequent runs.