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.3 is a maintenance release for the 5.9.x LTS line. It can be deployed as a direct upgrade from 5.9.2 with no breaking changes.Upgrade Path
5.9.2 → 5.9.3: Direct upgrade with no breaking changes.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.0 or 5.9.1 directly? Review the 5.9.2 deployment guidelines first — they include required steps for the organization-ID migration fix and manually marked Liquibase changesets that also apply when you skip 5.9.2.
Component versions
Core components
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 component versioning is unified in 5.9.2. All AI Platform services now ship under a single AI Platform version (10.9.0), including services that previously carried their own version lines (
doc-parser, doc-converter, data-privacy, speech-to-text, web-crawler, evals-judge). Their 5.9.2 version numbers are therefore not comparable with earlier columns — for example, doc-parser moves from 10.10.1 to 10.9.0 without losing anything. Component rows below use the plain service names introduced in 5.9.2 (the ai-platform- prefix is dropped — see AI Platform service naming); earlier columns show the same component under its previous name.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.3 introduces no new Kafka topics over 5.9.2. 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:- Update container images to the 5.9.3 versions listed in the table above.
- Deploy services using your standard deployment process.
- Verify deployment via FlowX.AI Designer → Platform Status.
Configuration changes
Events Gateway — Redis connection pool for blocking mode
The Events Gateway’s blocking read path is rebuilt on a dedicated Redis connection pool, fixing a connection leak that could previously require periodic Events Gateway restarts under sustained load. The new settings ship with working defaults — no action is required on upgrade.
If you previously set
EVENTS_REDIS_BLOCKDURATIONSECONDS explicitly, review whether the new default suits your setup. See the Events Gateway setup guide for the full configuration reference.
Integration Designer — workflow topic partitions
FLOWX_WORKFLOW_TOPICPARTITIONS (default 1) sets the number of partitions for auto-created workflow Kafka topics (used with FLOWX_WORKFLOW_CREATETOPICS). Existing topics are not modified; the setting applies to newly created topics only.
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.