2026.14 Infrastructure Changes — Unique AI Documentation

2026.14 Infrastructure Changes

Changes on Application environment

Change Environment Variable Name Application Default Value
(if env variable unset)
Example Required Applications Short Description
Added FEATURE_FLAG_AGENTIC_TABLE_INSERT_ROW_UN_17649 false true false - web-app-chat Enable insertion of rows in Agentic Table before or after a selected row.
Added FEATURE_FLAG_ENABLE_CODE_EXECUTION_FENCE_UN_17972 false true
can also be scoped by company id’s:
id_1, id_2,...
false - assistants-core Enable rendering of images and files in new iFrame with code toggle. html rendering via reflector.

File Access Migration Update

As part of this release, a file access migration in backend-service-ingestion will be executed for all customers, regardless of whether the File Access feature is currently enabled.

The data migration will initiate automatically during the deployment. This process updates existing indexes to support the new file access structure. It can take a bit longer than usual for the migrations step of the service to finish. The expected duration is approximately 10 minutes per 1 million chunks, depending on your environment size and file volume.

Switch from npx to pnpm exec in migration hooks

To improve consistency and performance across Node-based tooling, migration hooks have been updated to use pnpm exec instead of npx.

What changed:

Action required:

Example (backend-service-ingestion):

hooks:
  migration:
    command: |
      cd /home/node/app/services/node-ingestion/prisma; npx prisma migrate deploy --config ../prisma.config.ts;

replace with

hooks:
  migration:
    command: |
      cd /home/node/app/services/node-ingestion/prisma; pnpm exec prisma migrate deploy --config ../prisma.config.ts;

| Author | Solution Engineering |