Release Notes 3.2.91

Publication Date: January 8th 2026

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.91 release.

Upgrade Considerations

Please review the upgrade considerations provided here: https://gitana.io/documentation/gitana/3.2/guide/guide/docker/upgrades/3-2-91.html

With this upgrade:

• MongoDB 4.4 or above is required.
• You will need to perform a cold restart of your API cluster.

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.91 release.

We recommend this release for anyone using MongoDB 7 or beyond.

Enhancements

GraphQL

• The GraphQL executor service thread pool size is now configurable using the `gitana.graphql.threadpool.size` setting. The default is set to `16`.
• Faster performance for GraphQL with some cache refactoring.

MongoDB Compatibility

• Updated to the latest version of the MongoDB driver so as to gain advantages of various bug fixes and forward compatibility with future versions of MongoDB. This pulls in a lot of driver-level improvements that, all told, result in improved performance and better accuracy. It also introduces improved connection pooling which may resolve some issues customers have reported for some operations under high DB concurrency.

Bug Fixes

Job Halting

• Fix so that operations that perform distributed job halting (pausing or killing) work faster and more accurately by taking advantage of a refactored thread interruption mechanism for job workers.

Project Creation

• Fix so that failures during the transfer import phase of project creation willfully roll back in the event of project creation failure.

Search

• Fix so that search exceptions provide more detail to the requester.

User Interface

• Fix so that some URI generation for sub-items on Content page are corrected, no longer resulting in redirects to the project dashboard.
• Fix so that forms display correctly formatted invalidation messages when `minItems` or `maxItems` constraints are invalid.
• Fix so that tags are no included by default in find fields queries.
• Fix so that content types are filtered properly when retrieving content types from cache on subsequent fetches.