> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flowx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Deployment guidelines v6.0.0

> Component versions, Kafka topics, environment variables, and Helm chart changes for FlowX.AI 6.0.0, with the steps a self-hosted upgrade needs.

> [!NOTE]
>
> 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 6.0 is a feature release. On SaaS, FlowX applies every change on this page. Self-hosted deployments usually follow LTS releases and receive these changes with the next LTS release family. If you upgrade a self-hosted installation to 6.0.0, apply the changes below in the order given in [Migrating from v5.9.x to v6.0.0](https://docs.flowx.ai/release-notes/v6.x/v6.0.0-october-2026/migrating-from-v5.9-to-v6.0/migration-overview.md).

### Before you upgrade a self-hosted installation

* Set every AI service group flag explicitly. See [AI service groups in the Helm chart](#ai-service-groups-in-the-helm-chart).
* Deploy designer-user, the new `core` service. harness and ui-driver (`devtime`) and dynamic-classifier (`runtime`) deploy only if you turn their group on. See [New services](#new-services).
* Create the new database users and secrets for the services you deploy. Every installation needs the four new keys in `keycloak-flowx-realm-clients`. See [New databases and secrets](#new-databases-and-secrets).
* Give process-engine read access to the integration-designer bucket. See [New databases and secrets](#new-databases-and-secrets).
* If you turn on dynamic-classifier, set its bucket name and provide its 20Gi volume. See [Update your values](https://docs.flowx.ai/release-notes/v6.x/v6.0.0-october-2026/migrating-from-v5.9-to-v6.0/helm-chart.md#update-your-values).
* If you route with Kubernetes Ingress, move callers off the admin Ingress routes that the chart no longer creates. See [New databases and secrets](#new-databases-and-secrets).
* Create the new Kafka topics. If your cluster uses ACLs, also give the new clients of three existing topics access. See [New Kafka topics](#new-kafka-topics).
* Let audit-core reach Redis. It now uses Redis only to choose which replica runs its nightly cleanup job, not as a cache, and the chart connects it to the same Redis server as the other services. If you restrict which services can reach Redis, add audit-core. See [Configuring Redis](https://docs.flowx.ai/6.x/setup-guides/audit-setup-guide.md#configuring-redis).
* Set the personal-data encryption master key on integration-designer. See [Personal-data encryption master key](#new-required-secret-personal-data-encryption-master-key).
* Choose how Elasticsearch replicates new indices. See [Elasticsearch replica auto-expansion](#changed-default-elasticsearch-replica-auto-expansion).
* Add the MongoDB hosts on your private network that data sources use to `FLOWX_SSRFALLOWEDHOSTS`. See [nosql-db-runner host restrictions](#changed-behavior-nosql-db-runner-host-restrictions-cover-mongodb).
* Trust the certificates of the IMAP servers your email triggers read from. See [IMAPS certificate verification](#changed-default-imaps-certificate-verification-in-email-gateway).

Upgrading from 5.9.5 or earlier? Two changes from 5.9.6 also apply. See [Upgrading from an older patch release](#upgrading-from-an-older-patch-release).

## Component versions

The versions below are the component versions that make up FlowX.AI 6.0.0, next to FlowX.AI 5.9.6, the latest 5.9.x release a self-hosted installation upgrades from. A dash marks a component that is new since 5.9.6. On SaaS, FlowX manages these versions.

### Core components

| Component | 6.0.0 | 5.9.6 |
| - | - | - |
| **admin** | 11.132.0 | 10.152.14 |
| **advancing-controller** | 11.86.0 | 10.98.12 |
| **application-manager** | 11.143.0 | 10.159.3 |
| **audit-core** | 11.92.0 | 10.102.11 |
| **authorization-system** | 11.102.0 | 10.122.13 |
| **cms-core** | 11.114.0 | 10.113.13 |
| **data-search** | 11.87.0 | 10.92.11 |
| **data-sync** | 11.94.0 | 10.107.13 |
| **designer** | 11.252.0 | 10.285.4 |
| **designer-user** | 11.31.0 | - |
| **document-plugin** | 11.122.0 | 10.124.13 |
| **email-gateway** | 11.110.0 | 10.102.1 |
| **events-gateway** | 11.93.0 | 10.101.1 |
| **file-gateway** | 11.105.0 | 10.33.14 |
| **integration-designer** | 11.158.0 | 10.201.2 |
| **license** | 11.94.0 | 10.87.12 |
| **nosql-db-runner** | 11.98.0 | 10.101.13 |
| **notification-plugin** | 11.113.0 | 10.111.1 |
| **organization-manager** | 11.101.0 | 10.98.12 |
| **process-engine** | 11.137.1 | 10.174.17 |
| **runtime-manager** | 11.143.0 | 10.159.3 |
| **scheduler-core** | 11.89.0 | 10.94.11 |
| **task-management-plugin** | 11.109.0 | 10.112.12 |
| **webhook-gateway** | 11.102.0 | 10.69.12 |

### AI base components

| Component | 6.0.0 | 5.9.6 |
| - | - | - |
| **ai-gateway** | 11.118.1 | 10.35.13 |
| **embedder** | 11.7.0 | 10.11.2 |
| **knowledgebase-indexer-v2** | 11.7.0 | 10.11.2 |
| **knowledgebase-rag** | 11.7.0 | 10.11.2 |
| **doc-parser** | 11.7.0 | 10.11.2 |

### AI dev-time components

| Component | 6.0.0 | 5.9.6 |
| - | - | - |
| **ai-analyst** | 11.7.0 | 10.11.2 |
| **ai-architect** | 11.7.0 | 10.11.2 |
| **ai-assistant** | 11.7.0 | 10.11.2 |
| **ai-designer** | 11.7.0 | 10.11.2 |
| **ai-developer** | 11.7.0 | 10.11.2 |
| **harness** | 11.7.0 | - |
| **kb-enrichment** | 11.7.0 | 10.11.2 |
| **planner** | 11.7.0 | 10.11.2 |
| **ui-driver** | 11.252.0 | - |

### AI runtime components

| Component | 6.0.0 | 5.9.6 |
| - | - | - |
| **agent-builder** | 11.7.0 | 10.11.2 |
| **cee-pii** | 11.7.0 | - |
| **data-privacy** | 11.7.0 | 10.11.2 |
| **doc-converter** | 11.7.0 | 10.11.2 |
| **dynamic-classifier** | 11.7.0 | - |
| **evals-judge** | 11.7.0 | 10.11.2 |
| **speech-to-text** | 11.7.0 | 10.11.2 |
| **web-crawler** | 11.7.0 | 10.11.2 |

### AI extensions

| Component | 6.0.0 | 5.9.6 |
| - | - | - |
| **modpod** | 11.0.1 | 10.0.7 |
| **observatory-api** | 11.29.4 | 10.7.2 |
| **observatory-platform** | 11.29.4 | 10.7.2 |
| **observatory-web** | 11.29.4 | 10.7.2 |

In FlowX.AI 6.0, the Observatory components run on environments operated by FlowX. They aren't included in client deployments in this release.

### Embedded components

* **SpiceDB:** see the [5.9.0 deployment guidelines](https://docs.flowx.ai/release-notes/v5.x/v5.9.0-june-2026/deployment-guidelines-v5.9.md) for details.
* **Qdrant** (vector database): bundled in the `flowx-ai` Helm chart and deployed with the AI base group (see [AI service groups in the Helm chart](#ai-service-groups-in-the-helm-chart)). Its version is managed by the chart and not pinned here. See the [Qdrant setup guide](https://docs.flowx.ai/6.x/setup-guides/qdrant.md) for deployment and configuration.

### Renderers

The web SDKs ship at the **designer** version (`11.252.0` for FlowX.AI 6.0.0). The native iOS and Android renderers version independently.

| Component | 6.0.0 | 5.9.6 |
| - | - | - |
| **@flowx/angular-sdk** | 11.252.0 | 10.285.4 |
| **@flowx/angular-theme** | 11.252.0 | 10.285.4 |
| **@flowx/angular-ui-toolkit** | 11.252.0 | 10.285.4 |
| **@flowx/react-sdk** | 11.252.0 | 10.285.4 |
| **@flowx/react-theme** | 11.252.0 | 10.285.4 |
| **@flowx/react-ui-toolkit** | 11.252.0 | 10.285.4 |
| **@flowx/react-native-sdk** | 11.252.0 | 10.285.4 |
| **@flowx/react-native-theme** | 11.252.0 | 10.285.4 |
| **@flowx/react-native-ui-toolkit** | 11.252.0 | 10.285.4 |
| **@flowx/core-sdk** | 11.252.0 | 10.285.4 |
| **@flowx/core-theme** | 11.252.0 | 10.285.4 |
| **solution-portal** | 11.252.0 | 10.285.4 |
| **iOS renderer** | 11.6.0 | 10.9.2 |
| **Android renderer** | 11.18.0 | 10.10.2 |

The **solution-portal** container app tracks the designer version.

***

## Configuration changes

This section compares environment variables, Kafka topics, and the `flowx-ai` Helm chart with FlowX.AI 5.9.6. It includes the changes that reached SaaS in 5.10 to 5.13, so a self-hosted upgrade from 5.9.6 needs only this page.

### New Kafka topics

Compared with 5.9.6, create these 42 topics. Create all of them, whatever your group flags: topics for services you don't deploy stay unused. On SaaS they are created and managed automatically.

**AI nodes as durable jobs:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.ai-platform.agent-node.job.request.v1` | integration-designer → agent-builder |
| `ai.flowx.ai-platform.agent-node.job.response.v1` | agent-builder → integration-designer |
| `ai.flowx.ai-platform.agent-node.job.progress.v1` | agent-builder → integration-designer |
| `ai.flowx.ai-platform.agent-node.job.cancel.v1` | integration-designer → agent-builder |
| `ai.flowx.ai-platform.agent-node.job.dlq.v1` | agent-builder → none (dead-letter topic) |

**Deep research node:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.ai-platform.deep-research.job.request.v1` | integration-designer → agent-builder |
| `ai.flowx.ai-platform.deep-research.job.response.v1` | agent-builder → integration-designer |
| `ai.flowx.ai-platform.deep-research.job.dlq.v1` | agent-builder → none (dead-letter topic) |

**Validation findings:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.application-version.validation-findings.request-admin.v1` | application-manager → admin |
| `ai.flowx.application-version.validation-findings.request-cms.v1` | application-manager → cms-core |
| `ai.flowx.application-version.validation-findings.request-document-plugin.v1` | application-manager → document-plugin |
| `ai.flowx.application-version.validation-findings.request-integration.v1` | application-manager → integration-designer |
| `ai.flowx.application-version.validation-findings.request-notification-plugin.v1` | application-manager → notification-plugin |
| `ai.flowx.application-version.validation-findings.request-application-manager.v1` | application-manager → application-manager |
| `ai.flowx.application-version.validation-findings.response.v1` | admin, cms-core, document-plugin, integration-designer, notification-plugin → application-manager |
| `ai.flowx.application-version.validation-findings.job-completed.v1` | application-manager → harness |

**Structured template data model:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.plugin.template-data-model.migration.v1` | admin → document-plugin, notification-plugin |
| `ai.flowx.application-version.sync.document-template.in.v1` | application-manager → document-plugin |
| `ai.flowx.application-version.sync.notification-template.in.v1` | application-manager → notification-plugin |
| `ai.flowx.application-version.correction-after-app-operation.document-template.request.v1` | application-manager → document-plugin |
| `ai.flowx.application-version.correction-after-app-operation.notification-template.request.v1` | application-manager → notification-plugin |

**Runtime content import and export:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.runtime-content.task.request.v1` | application-manager → integration-designer |
| `ai.flowx.runtime-content.task.response.v1` | integration-designer → application-manager |
| `ai.flowx.ai-platform.knowledgebase.job.request.v1` | integration-designer → embedder |
| `ai.flowx.ai-platform.knowledgebase.job.response.v1` | embedder → integration-designer |

**Document classification and extraction:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.dynamic-classifier.job.request.v1` | integration-designer → dynamic-classifier |
| `ai.flowx.dynamic-classifier.job.response.v1` | dynamic-classifier → integration-designer |
| `ai.flowx.dynamic-classifier.job.dlq.v1` | dynamic-classifier → none (dead-letter topic) |
| `ai.flowx.plugin.document.trigger.ml-archive-extract.v1` | integration-designer → document-plugin |
| `ai.flowx.plugin.document.ml-archive-extract.results.v1` | document-plugin → integration-designer |
| `ai.flowx.ai-platform.doc-parser.job.response.ml.v1` | doc-parser → integration-designer |

**Event-triggered workflows:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.build.trigger-subscription-change.in.v1` | admin, integration-designer → application-manager |
| `ai.flowx.core.trigger.start-for-event.workflow.v1` | email-gateway, webhook-gateway → integration-designer |

**Workflow schedules:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.build.workflow-schedules.updates.in.v1` | integration-designer → runtime-manager |
| `ai.flowx.core.notify.timer-event-schedule.state.v1` | scheduler-core → runtime-manager |

**Bulk instance migration and move token:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.core.trigger.instance-migration.batch.v1` | process-engine → process-engine |
| `ai.flowx.core.trigger.token-move.batch.v1` | process-engine → process-engine |

**Run auditing:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.core.run.segment.v1` | process-engine, integration-designer → audit-core |
| `ai.flowx.core.runtime.failure.v1` | process-engine, integration-designer → audit-core |

**Designer notifications and preferences:**

| Topic | Producer → Consumer |
| - | - |
| `ai.flowx.designer-user.notifications.v1` | application-manager, process-engine → designer-user |
| `ai.flowx.eventsgateway.user.notifications.v1` | designer-user → events-gateway |
| `ai.flowx.designer-user.user-preferences.v1` | designer-user → designer-user |

> [!NOTE]
>
> If your Kafka cluster uses ACLs, also give the new clients of these existing topics access:
>
> * `ai.flowx.application-version.sync.out.v1`: document-plugin and notification-plugin
> * `ai.flowx.application-version.correction-after-app-operation.response.v1`: document-plugin and notification-plugin
> * `ai.flowx.application-version.resources-usages.sub-res-validation.response.v1`: document-plugin

### New services

Compared with 5.9.6, the `flowx-ai` Helm chart adds four services. On SaaS they are provisioned and managed by FlowX.

| Service | Group | What it does | Dependencies |
| - | - | - | - |
| designer-user | `core` | Stores Designer user preferences, such as the last-used workspace, and delivers Designer notifications | MongoDB, Redis, Kafka |
| harness | `devtime` | Runs the Developer Agentic Harness | PostgreSQL, Redis, Kafka |
| ui-driver | `devtime` | Renders UI flows in the background for the Developer Agentic Harness | None |
| dynamic-classifier | `runtime` | Classifies documents with trained models | PostgreSQL, a persistent volume, Kafka |

The databases, secrets, and volume are in [New databases and secrets](#new-databases-and-secrets).

The harness reuses the platform's existing Redis, so nothing new is provisioned. It uses Redis to stream a running turn to every open Designer session and to cancel a turn from any harness pod. Without Redis, turns still run, but live progress and cancellation across pods don't work.

The harness also consumes the existing `ai.flowx.llm.config.changed.v1` topic, so a change to an organization's AI model settings reaches it right away. Without Kafka, it picks up the change when its cache expires.

### AI service groups in the Helm chart

The `flowx-ai` Helm chart groups the services into four groups. Each group has its own flag, `groups.<group>.enabled`:

| Group | Services |
| - | - |
| `core` | Core platform services |
| `base` | The AI base: ai-gateway, doc-parser, embedder, knowledgebase-indexer-v2, knowledgebase-rag, and the bundled Qdrant |
| `devtime` | ai-analyst, ai-architect, ai-assistant, ai-designer, ai-developer, harness, kb-enrichment, planner, ui-driver |
| `runtime` | agent-builder, data-privacy, doc-converter, dynamic-classifier, evals-judge, speech-to-text, web-crawler. cee-pii is in this group but needs `services.cee-pii.enabled: true` as well |

The groups are the same as in 5.9.6. The 6.0.0 chart adds designer-user to `core`, harness and ui-driver to `devtime`, and cee-pii and dynamic-classifier to `runtime`. The `base` group is unchanged.

Set all four flags in your values. `core` is `true` in every combination:

| To install | `base` | `devtime` | `runtime` |
| - | - | - | - |
| Core services only | `false` | `false` | `false` |
| Core, base, and devtime services | `true` | `true` | `false` |
| Core, base, and runtime services | `true` | `false` | `true` |
| All services | `true` | `true` | `true` |

> [!WARNING]
>
> **Set every group flag explicitly for self-hosted upgrades.** Don't rely on the chart's group defaults. The `devtime` and `runtime` services call the AI base services, so turn `base` on whenever either of them is on. The chart doesn't check this for you.

### New databases and secrets

Compared with the `flowx-ai` Helm chart in 5.9.6, these services need new databases. Create a database only if its service's group is on. designer-user is in `core`, so every installation needs its database:

| Service | Group | Database user | Secret |
| - | - | - | - |
| agent-builder | `runtime` | PostgreSQL `agent_builder` | `flowx-postgres-agent-builder` |
| dynamic-classifier | `runtime` | PostgreSQL `dynamic_classifier` | `flowx-postgres-dynamic-classifier` |
| harness | `devtime` | PostgreSQL `harness` | `flowx-postgres-harness` |
| designer-user | `core` | MongoDB `designer-user` | `mongodb-designer-user-designer-user` |

Each database has the same name as its user. Each secret holds the user's password under the key `password`.

The webhook-gateway also connects to the existing `app-runtime` MongoDB database with the `app-runtime` user.

The `keycloak-flowx-realm-clients` secret needs four new keys, one for each new service account:

| Secret key | Keycloak client |
| - | - |
| `KEYCLOAK_DESIGNER_USER_CLIENT_SECRET` | `flowx-designer-user-sa` |
| `KEYCLOAK_AI_HARNESS_CLIENT_SECRET` | `flowx-ai-harness-sa` |
| `KEYCLOAK_NOTIFICATION_PLUGIN_CLIENT_SECRET` | `flowx-notification-plugin-sa` |
| `KEYCLOAK_DOCUMENT_PLUGIN_CLIENT_SECRET` | `flowx-document-plugin-sa` |

Other chart changes:

* **process-engine** needs read-only access (`s3:GetObject`) to the integration-designer bucket, to download the Kafka payloads that integration-designer stores there. The chart reads the access key ID from `global.flowx.s3.credentials.processEngine.accessKey` (default `flowx-process-engine-accesskey`) and the secret access key from the `flowx-process-engine-s3` secret, key `SecretAccessKey`.
* **dynamic-classifier** stores its data on a 20Gi `ReadWriteOnce` persistent volume claim, `dynamic-classifier-data`, and uses the `Recreate` deployment strategy, so an upgrade stops the old pod before the new one starts.
* **dynamic-classifier** reads an OpenAI API key for its LLM judge from the `dynamic-classifier-openai` secret, key `OPENAI_API_KEY`. The secret is optional: without it, the pod still starts and classification keeps working.
* The chart no longer creates an admin Ingress for doc-converter, data-privacy, speech-to-text, web-crawler, and dynamic-classifier. ai-gateway keeps its own.

### New required secret: personal-data encryption master key

The Mask Personal Data and Restore Personal Data nodes encrypt the placeholder map they keep during a workflow run. The key material comes from a new integration-designer variable with **no default**: without it, the mask and restore nodes fail rather than encrypt personal data with a published value. On SaaS this secret is provisioned and managed by FlowX.

New integration-designer variables:

| Environment Variable | Description | Default Value |
| - | - | - |
| `FLOWX_PII_ENCRYPTION_MASTER_KEY` | Master secret the mask and restore nodes derive their encryption key from. Any non-empty string; use a strong random value and store it as a secret. Must be identical across all pods and stable over time: changing it invalidates every in-flight placeholder map | none (required) |
| `FLOWX_PII_ENCRYPTION_KEY_ID` | Label recorded on new placeholder-map entries so a future migration can support key rotation. Only the configured key is held today | `k1` |
| `FLOWX_PII_MAP_TTL` | How long a masked value stays restorable. Bounds exposure when a run ends without reaching the instance-end cleanup hooks; enforced by a MongoDB TTL index | `PT24H` |

### New object storage bucket: runtime content

Runtime content export and import stores its files in a new shared bucket, `runtime-content-bucket`. Application Manager creates the bucket on first use, Integration Designer writes export files and reads imports there, and the embedder reads and writes Knowledge Base vectors at the paths each request names. Grant all three services access to the bucket.

Browsers upload import files and download export files directly, through presigned URLs that Application Manager signs. By default it signs them with the internal storage endpoint, which only pods can reach, so set `APPLICATION_FILESTORAGE_S3_PRESIGNSERVERURL` to a storage endpoint that browsers can reach.

New variables on application-manager and integration-designer. Set the bucket on both, and the presign settings on application-manager only:

| Environment Variable | Description | Default Value |
| - | - | - |
| `APPLICATION_FILESTORAGE_S3_RUNTIMECONTENTBUCKET` | Bucket for runtime content export and import files | `runtime-content-bucket` |
| `APPLICATION_FILESTORAGE_S3_PRESIGNSERVERURL` | Storage endpoint used to sign the presigned upload and download URLs. Leave empty to sign with the internal storage endpoint | empty |
| `APPLICATION_FILESTORAGE_S3_PRESIGNREGION` | Region used to sign the presigned URLs | `us-east-1` |

For the full list of buckets, see [Data architecture](https://docs.flowx.ai/6.x/docs/platform-overview/data-architecture.md#s3-compatible-object-storage-buckets).

### Changed default: Elasticsearch replica auto-expansion

New process instance indices and new audit log indices now use the Elasticsearch `auto_expand_replicas` setting, with a default of `0-1`. Elasticsearch keeps 0 replicas when the cluster has one data node and 1 replica when it has two or more, and adjusts the count as nodes join or leave. On SaaS, Elasticsearch is managed by FlowX.

New process-engine and audit-core variable:

| Environment Variable | Description | Default Value |
| - | - | - |
| `FLOWX_ELASTICSEARCH_INDEXSETTINGS_AUTOEXPANDREPLICAS` | Replica range that Elasticsearch applies to new indices. Set to `false` to use the fixed `FLOWX_ELASTICSEARCH_INDEXSETTINGS_REPLICAS` value instead | `0-1` |

* **Overrides the fixed replica count:** while auto-expansion is on, `FLOWX_ELASTICSEARCH_INDEXSETTINGS_REPLICAS` has no effect on new indices.
* **New indices only:** the setting applies to the `process_instance` index and index template and to the audit logs data stream template. Existing indices keep their current settings.
* **Disk usage:** on clusters with two or more data nodes, the replica roughly doubles the disk space these indices use.

> [!WARNING]
>
> **Breaking change for self-hosted upgrades.** A deployment that pins a fixed replica count, for example `FLOWX_ELASTICSEARCH_INDEXSETTINGS_REPLICAS=3`, loses it on new indices unless it also sets `FLOWX_ELASTICSEARCH_INDEXSETTINGS_AUTOEXPANDREPLICAS=false`. On multi-node clusters, check free disk space before upgrading.

To apply auto-expansion to indices created before the upgrade, update their settings once:

```http theme={"dark"}
PUT process_instance*,.ds-audit-logs*/_settings
{"index": {"auto_expand_replicas": "0-1"}}
```

### Changed behavior: nosql-db-runner host restrictions cover MongoDB

The host restriction that relational data sources already had now applies to external MongoDB connections too. The nosql-db-runner checks every address a MongoDB host resolves to, including replica-set members and SRV targets, and rejects the connection if any of them is private. For FlowX Database and Unmanaged MongoDB data sources alike, it also rejects `UPDATE`, `UPDATE_MANY`, `DELETE`, and `DELETE_MANY` operations with a missing or empty filter. To match every document, pass `{"_id": {"$exists": true}}`.

nosql-db-runner variables (both already existed for relational data sources):

| Environment Variable | Description | Default Value |
| - | - | - |
| `FLOWX_SSRFALLOWEDHOSTS` | Hosts or CIDR blocks, separated by commas, that may connect even though they resolve to a private address. Addresses on the local machine or in a link-local range stay blocked | empty |
| `FLOWX_SSRFPROTECTIONENABLED` | Turns the host restriction on or off | `true` |

> [!WARNING]
>
> **Breaking change for self-hosted upgrades.** Unmanaged MongoDB data sources that point to a host on a private network stop connecting after the upgrade. Add those hosts to `FLOWX_SSRFALLOWEDHOSTS`.

### Changed behavior: name placeholders in data-privacy

When data-privacy masks a person's name, the placeholder now carries the gender, for example `<NAME_F_1>` or `<NAME_M_1>`. When the name doesn't show the gender, the placeholder stays `<NAME_1>`. Prompts or scripts that match the old placeholder form need updating.

### Changed behavior: Workspace operations editor role replaced

The upgrade replaces the Workspace operations editor role with the [Workspace corrective actions editor](https://docs.flowx.ai/6.x/setup-guides/access-management/roles-permissions-matrix.md#workspace-corrective-actions-editor-permission-matrix) role. Users and groups that had the old role get the new one automatically and keep access to process instance migration and move token. No action is needed.

### New environment variables: audit index retention

The Audit service can now delete old audit data and roll over by shard size. Both settings are off by default, so the Audit service doesn't delete data unless you set a retention period.

New audit-core variables:

| Environment Variable | Description | Default Value |
| - | - | - |
| `FLOWX_ELASTICSEARCH_INDEXRETENTIONDAYS` | Days after a backing index rolls over before it's deleted | Not set: indices are never deleted |
| `FLOWX_ELASTICSEARCH_INDEXROLLOVERMAXPRIMARYSHARDSIZE` | Also roll over when a primary shard reaches this size, such as `50gb` | Not set: roll over by age only |

> [!WARNING]
>
> When you first set `FLOWX_ELASTICSEARCH_INDEXRETENTIONDAYS`, the Audit service also deletes backing indices that rolled over more than that many days ago. See [Configuring Elasticsearch](https://docs.flowx.ai/6.x/setup-guides/audit-setup-guide.md#configuring-elasticsearch).

### Changed default: IMAPS certificate verification in email-gateway

The email-gateway now verifies the certificate of every IMAPS server it connects to. A server must present a certificate signed by a trusted authority and matching its host name.

New email-gateway variable:

| Environment Variable | Description | Default Value |
| - | - | - |
| `EMAILGATEWAY_IMAP_SSLTRUSTEDHOSTS` | Mail hosts that skip certificate verification, separated by spaces or commas. Use `*` to skip it for every host | empty |

> [!WARNING]
>
> **Breaking change for self-hosted upgrades.** Email triggers that read from an IMAP server with a self-signed, private-CA, or mismatched certificate stop connecting after the upgrade. Add the server's CA to the email-gateway trust store, or list the host in `EMAILGATEWAY_IMAP_SSLTRUSTEDHOSTS`.

### Changed default: AI node retry

AI nodes without retry settings of their own now retry when a dependency is temporarily unavailable, such as an LLM provider outage, a rate limit, or a lost connection. Permanent errors aren't retried, and deep research nodes never retry by default. A node's own retry settings replace the default.

New integration-designer variables:

| Environment Variable | Description | Default Value |
| - | - | - |
| `FLOWX_WORKFLOW_AINODEDEFAULTRETRY_ENABLED` | Turns the default retry for AI nodes on or off | `true` |
| `FLOWX_WORKFLOW_AINODEDEFAULTRETRY_MAXATTEMPTS` | Maximum retry attempts | `10` |
| `FLOWX_WORKFLOW_AINODEDEFAULTRETRY_BACKOFFPERIOD` | Wait between attempts, as an ISO-8601 duration | `PT30S` |

### Upgrading from an older patch release

Upgrading from 5.9.5 or earlier? Apply the [5.9.6 deployment guidelines](https://docs.flowx.ai/release-notes/v5.x/v5.9.6-october-2026/deployment-guidelines-v5.9.6.md#build-redeployment-retries) as well. Two 5.9.6 changes affect the upgrade:

* **Build redeployment retries:** the queue of build deployments waiting for a retry moved from Redis to the application-manager PostgreSQL database, with a new topic, `ai.flowx.build.deployment-failed.v1`. Deployments waiting for a retry in Redis when you upgrade aren't moved to the new queue. Re-publish those builds after the upgrade.
* **advancing-controller management port:** `MANAGEMENT_SECURITY_ENABLED` is no longer read. Actuator endpoints on the management port, including Prometheus, answer without authentication.

> [!WARNING]
>
> Keep the advancing-controller management port, `8081`, off any public ingress.

> [!NOTE]
>
> For previous FlowX.AI releases, please refer to the [Release Notes overview](https://docs.flowx.ai/release-notes/overview.md).


## Related topics

- [FlowX.AI 6.0.0 Release Notes](https://docs.flowx.ai/release-notes/v6.x/v6.0.0-october-2026/v6.0.0-october-2026.md)
- [Helm chart](https://docs.flowx.ai/release-notes/v6.x/v6.0.0-october-2026/migrating-from-v5.9-to-v6.0/helm-chart.md)
- [Deployment guidelines v5.9.6](https://docs.flowx.ai/release-notes/v5.x/v5.9.6-october-2026/deployment-guidelines-v5.9.6.md)
- [Deployment guidelines v5.9.7](https://docs.flowx.ai/release-notes/v5.x/v5.9.7-november-2026/deployment-guidelines-v5.9.7.md)
- [iOS SDK](https://docs.flowx.ai/release-notes/v6.x/v6.0.0-october-2026/migrating-from-v5.9-to-v6.0/ios.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.