2026.10 Infrastructure Changes

3 min read

💥 Breaking Changes Troubleshooting

ADDED

Theme needs SCOPE_MANAGEMENT_BACKEND_API_URL

Invalid input: expected string, received undefined
  → at scopeManagementBackendApiUrl

Set SCOPE_MANAGEMENT_BACKEND_API_URL in web-app-theme.

Changes on Application environment

Change	Environment Variable Name	Application Default Value (if env variable unset)	Example	Required	Applications	Short Description
Added	`SCOPE_MANAGEMENT_BACKEND_API_URL`	`undefined`	`https://api.uat1.unique.app/scope-management`	`true` bREAKING	`web-app-theme`	Scope Management API URL to manage SCIM keys in the frontend.
Added	`WHISPER_OX_API_KEY`	(empty — no auth)	`my-secret-key`	`false`	`backend-service-speech`	Optional API key sent to the Whisper OX transcription server. When set, the key is included in requests to the `/transcribe` endpoint.
Added	`WHISPER_OX_API_KEY_HEADER`	`X-API-Key`	`Authorization`	`false`	`backend-service-speech`	Header name used to send the Whisper OX API key. Only used when `WHISPER_OX_API_KEY` is set.
Added	`FEATURE_FLAG_AGENTIC_TABLE_RERUN_BUTTON_UN_13901`	`false`	`true`	`false`	`web-app-chat`	Enables ability to re-run the whole agentic table sheet
Added	`FEATURE_FLAG_AGENTIC_TABLE_ROW_RERUN_UN_14903`	`false`	`true`	`false`	`web-app-chat`	Enables ability to re-run a single row
Added	`FEATURE_FLAG_AGENTIC_TABLE_NEW_FILES_DROPDOWN_UN_12713`	`false`	`false`	`false`	`web-app-chat`	New design for the Sources and Questions list which allows deletion of sources + questions in an Agentic Table Sheet
Added	`FEATURE_FLAG_AGENTIC_TABLE_ENABLE_NEW_SHARING_UI_UN_16758`	`false`	`false`	`false`	`web-app-chat`	Adds fine-grained sharing controls for managing and editing Agentic Table Sheets.
Added	`FEATURE_FLAG_ENABLE_COLUMN_MULTI_SELECT_UN_16912`	`false`	`true`	`false`	`web-app-knowledge-upload`	Allows multi-selection of files in Knowledgebase column view
Added	`FEATURE_FLAG_REFERENCE_STYLE_REVAMP_UN_16900`	`false`	`true`	`false`	`web-app-chat`	Changes the visualisation of the references in chat showing up to three before aggregation
Added	`FEATURE_FLAG_REFERENCE_STYLE_2_UN_16900`	`false`	`true`	`false`	`web-app-chat`	Changes the visualisation of the references in chat to numbers instead of text showing up to five before aggregation. Note: Requires `FEATURE_FLAG_REFERENCE_STYLE_REVAMP_UN_16900` turned on
Added	`FEATURE_FLAG_ENABLE_CODE_EXECUTION_UN_17498`	`false`	`true`	`false`	`backend-service-chat` `web-app-admin`	Enables the configuration and usage of the code execution tool when setting up spaces (assistants). Note: Requires `SOURCE_AVAILABLE_TOOLS_REMOTELY` from `2026.08` in `backend-service-chat` when turned on.
Added	`FEATURE_FLAG_ENABLE_END_USER_SPACE_UN_8855`	`false`	`true`	`false`	`web-app-chat` `web-app-admin`	This flag enables admin modification for end user space toggle visibility, end user spaces creation and management
Added	`FEATURE_FLAG_ENABLE_NEW_ANSWER_FORMATTING_UN_14392`	`false`	`true`	`false`	`assistants-core` `web-app-chat`	This feature flag enables the correct behaviour of message logs in the new chat UI. Note:The flag `FEATURE_FLAG_ENABLE_NEW_ANSWERS_UI_UN_14411` must be enabled for this to work.
Added	`FEATURE_FLAG_ENABLE_ELICITATION_UN_15809`	`false`	`true`	`false`	`assistants-core`	This flag enables displaying elicitation calls. Currently used for approval of web search queries.
Modified	FILE_ACCESS_REBUILD_BATCH_SIZE	250	250	`false`	`backend-service-ingestion`	Sets how many file-access–related records are processed in one batch during the file access rebuild maintenance job.
Modified	FILE_ACCESS_REBUILD_REBUILD_ALL	`false`	`false`	`false`	`backend-service-ingestion`	Controls which content is included in the file access rebuild

Deployment Remark

In the release 2026.10 there is a dependency in the order of the application deployments. The application backend-service-scope-management needs to be deployed before the application backend-service-ingestion.

Reason is that the Scope and Scope Access Migration, of backend-service-ingestion, requires the updated backend-service-scope-management.

Zitadel Vulnerability patch

Upgrade Zitadel to v3.4.7 to fix vulnerability issue.

File Access Migration Update

As part of this release, we will run a file access migration for all customers, regardless of whether the File Access feature is enabled or not.

After deployment and completing the below “Node ingestion hooks update“ the migration will not begin automatically and will be launched manually. This process updates existing indexes to support the new file access structure. Depending on the size of your environment and the volume of files, it may take approximately 12 to 24 hours to complete.

The migration is designed to run safely in the background. During this window, you may notice slower ingestion speeds. Aside from that, no other performance degradation is expected.

Scope and Scope Access Migration update

As part of this release we will migrate the scope and scope access data from backend-service-scope-management to backend-service-ingestion.

To maintain backward compatibility backend-service-scope-management will still expose the resolvers and call backend-service-ingestion.

The below “Node ingestion hooks update“ needs to be done before deployment.

During the running of the data migration the operations that require scopes and scope accesses will not complete and the end user will see an error.

Depending on the size of your environment and the volume of data, it may take approximately 1 to 2 hours to complete.

Required Node ingestion hooks update

A new data migration hook has been added to the backend-service-ingestion. The migration command in the migration hook in the default values of the service need to be adjusted.

// search for
cd /home/node/app/services/node-ingestion/prisma; npx prisma migrate deploy --config ../prisma.config.ts;

// replace with
cd /home/node/app/services/node-ingestion/prisma; npx prisma migrate deploy --config ../prisma.config.ts; cd /home/node/app/services/node-ingestion/dist; RUNNING_MODE=data-migration  node /home/node/app/services/node-ingestion/dist/main.js;

The final result should look like this in the default values of backend-service-ingestion:

hooks:
  migration:
    command: |
      cd /home/node/app/services/node-ingestion/prisma; npx prisma migrate deploy --config ../prisma.config.ts; cd /home/node/app/services/node-ingestion/dist; RUNNING_MODE=data-migration  node /home/node/app/services/node-ingestion/dist/main.js;
    enabled: true

Author	Solution Engineering