After upgrading to a new platform version, always ensure that your installed component versions match the versions specified in the release notes. To verify this, navigate to FlowX.AI Designer → Platform Status.
Upgrade overview
FlowX.AI 5.9.5 is a maintenance release for the 5.9.x LTS line. The upgrade from 5.9.4 is non-breaking and requires no data migration. The headline addition, native PostgreSQL partitioning, is opt-in: deployments that never enabled data partitioning are not affected. Review Configuration changes before you deploy.Upgrade Path
5.9.4 → 5.9.5: Direct upgrade. No data migration is required.Self-hosted customers still on the 5.1.x LTS upgrade directly to the 5.9.x line. See Migrating from 5.1 LTS.
Upgrading from 5.9.3 or earlier directly? Review the 5.9.4 deployment guidelines first: the Helm image registry split applies when you skip 5.9.4. Upgrading from 5.9.0, 5.9.1, or 5.9.2, also review the 5.9.2 deployment guidelines for the organization-ID migration fix and manually marked Liquibase changesets.
Component versions
Core components
* The reporting plugin is an optional add-on and is versioned independently of the platform, so its numbering does not follow the other components. It moved from the
0.2.x scheme to 10.x after 5.9.0. Pin the version listed for your release.
Embedded components
- SpiceDB: see the 5.9.0 deployment guidelines for details.
- Qdrant (vector database): bundled in the AI Platform Helm chart; its version is managed by the chart and not pinned here. See the Qdrant setup guide for deployment and configuration.
Renderers
AI components
FlowX.AI groups AI services into four tiers by deployment role. AI Base components are the foundation; AI Runtime and AI Dev Time components both require Base to be installed first; AI Extensions are optional add-ons layered on top.AI Base components
AI Runtime components
AI Dev Time components
AI Extensions
For the plugins matrix, refer to the 5.9.0 deployment guidelines.
Kafka topics
5.9.5 introduces no new Kafka topics over 5.9.4. For the full multi-release topic matrix, see the 5.9.0 deployment guidelines.
Deployment notes
Standard deployment
This maintenance release follows standard FlowX.AI deployment procedures:- Review Configuration changes: everything new in this release is opt-in or ships with a safe default, so no values change is required for a standard upgrade.
- Update container images to the 5.9.5 versions listed in the table above.
- Deploy services using your standard deployment process.
- Verify deployment via FlowX.AI Designer → Platform Status.
Configuration changes
Native PostgreSQL partitioning (opt-in)
Process-instance archiving on PostgreSQL can now use native declarative partitions instead of the legacy copy-based mechanism. Data partitioning itself remains off by default (FLOWX_DATA_PARTITIONING_ENABLED is false), so deployments that never enabled it are not affected.
New process-engine variables:
Document plugin: processing size limits
The document plugin now enforces size limits on archive, encryption, and extraction operations. Input over the limit is rejected instead of processed. The defaults are generous; override them only if your documents legitimately exceed them.Integration Designer: workflow output size guard
Workflow output published to Kafka is now size-checked before sending. A root workflow output that exceeds the limit fails the workflow run with the failure typeoutputTooLargeForKafka instead of being silently dropped by the broker’s message-size limit. The check applies to root workflow outputs on automatic and default-path completion; subworkflow outputs are not checked.
Advancing datasource metrics
The process engine and Integration Designer now register their advancing datasource under a named connection pool (advancing), so its metrics are distinguishable from the main datasource pool in Prometheus. No configuration action is required.
Confirm any required configuration changes against the setup guides before upgrading.
Third-party supported component versions
Within each version line listed below, versions that have reached upstream end of life are not supported, even though their major/minor is listed.
(*) Required only if using indexing via Kafka. Multiple sink connector implementations also work, as long as they are compatible with both the deployed Kafka and Elasticsearch version.
The table lists version lines, not individual versions. A version is supported for as long as its vendor still supports it, so check the version you plan to deploy against that vendor’s lifecycle page before committing to it. When a version reaches upstream end of life it is no longer supported; upgrade that component to keep your deployment on a supported configuration. Versions can also be added during the family’s lifetime as FlowX validates them.
For previous FlowX.AI releases, please refer to the Release Notes overview.