May 2026 Releases

Internal "Déjà Vu" object caching was retaining previous Component template settings.

When a Component template was initially applied or removed, this was not reflected in the CMS administration interface.

The Déjà Vu cache is now refreshed when Component templates are applied.

Changes to the component templates are now reflected immediately in the administration interface.

Losing the connection after the cache expired blocked session verification.

Keys for JWT signature verification are now stored, using earlier values if the key service is unavailable.

If Squiz DXP connectivity is lost, valid sessions remain active, so sites stay available.

Squiz Content Management did not have a facility to check if the submission log cron succeeded or failed to send an email report.

A log now records the submission log email status so users can check it.

Template changes moved content out of a newly locked template zone (an area where editing is restricted) and into an unlocked zone (where editing is allowed).

Content saved to the page went missing because it was not correctly matched to node(s) in the new zone by nodeId, nor did it appear in Unused Content. The editors couldn’t recover missing content.

The saved page content for any template-managed blocks that have been moved now correctly appear in the new location. Any blocks leftover in the newly locked zone will appear in unused content.

Improper handling of errors from the content service when canceling the safe edit status caused the status change to continue even when errors occurred. Squiz Content Management and the content service became out of sync, preventing the page from being edited.

The status change now fails or reverts if errors occur in the content service during draft updates. Squiz Content Management and content service now sync when canceling safe edit.

Fixed an issue where webhook microservice pods (small, self-contained services that handle webhooks) entered an Error state and restarted when a sample request was sent with the query parameter ?raw=true and the content type was set to multipart/form-data (a format for sending files and data in one request).

Fixed an issue where calling a flow’s webhook URL could still run a flow after the Webhook trigger had been replaced by a Polling trigger.

Fixed an issue where applying a storage container quota could fail when the quota limit was exceeded, and the container rollback process then set the recorded usage value to null.

Fixed an issue where deleting an active flow did not release container usage.

Fixed an issue where calling v2/flows/:id/run-now erroneously created an execution associated with the Webhook trigger.

Initial component release: copy workspace and flow actions.

Initial component release with these key features:

Improved logging for Axios, with updated dependencies:

Read the May 2026 new features to learn more about serving 404s on unpublished pages.

Read the May 2026 new features to learn more about marking your favorite flows in the Integrations flows list.

Read the May 2026 new features to learn more about the trigger type indicator.