Skip to content

Upgrade from v1.16 to v1.17 errors making twenty server crashΒ #18082

@Rom1an

Description

@Rom1an

Bug Description

During an upgrade from v1.16 to v1.17, we encounter an error that prevent the upgrade to finish and make twenty server crash:

[Nest] 99  - 02/19/2026, 10:46:41 AM     LOG [DatabaseConfigDriver] [INIT] Loading initial config variables from database
[Nest] 99  - 02/19/2026, 10:46:41 AM     LOG [DatabaseConfigDriver] [INIT] Config variables loaded: 0 values found in DB, 72 falling to env vars/defaults
[Nest] 99  - 02/19/2026, 10:46:41 AM     LOG [UpgradeCommand] Initialized upgrade context with:
   - currentVersion (migrating to): 1.17.0
   - fromWorkspaceVersion: 1.16.0
   - 10 commands

[...]

[Nest] 99  - 02/19/2026, 10:44:04 AM     LOG [DeleteFileRecordsAndUpdateTableCommand] Starting deletion of file records for workspace 7a36809e-0067-4bdb-a8d9-42b3093c23f0
[Nest] 99  - 02/19/2026, 10:44:04 AM     LOG [DeleteFileRecordsAndUpdateTableCommand] No file records found for workspace 7a36809e-0067-4bdb-a8d9-42b3093c23f0, skipping
query failed: ALTER TABLE "core"."file" DROP COLUMN "name"
error: error: column "name" of relation "file" does not exist
[Nest] 99  - 02/19/2026, 10:44:04 AM   ERROR [DeleteFileRecordsAndUpdateTableCommand] Rolling back updateFileTable: column "name" of relation "file" does not exist
query failed: ALTER TABLE "core"."file" ADD CONSTRAINT "IDX_APPLICATION_PATH_WORKSPACE_ID_APPLICATION_ID_UNIQUE" UNIQUE ("workspaceId", "applicationId", "path")
error: error: relation "IDX_APPLICATION_PATH_WORKSPACE_ID_APPLICATION_ID_UNIQUE" already exists
[Nest] 99  - 02/19/2026, 10:44:04 AM   ERROR [DeleteFileRecordsAndUpdateTableCommand] Rolling back addFileEntityUniqueConstraint: relation "IDX_APPLICATION_PATH_WORKSPACE_ID_APPLICATION_ID_UNIQUE" already exists
[Nest] 99  - 02/19/2026, 10:44:04 AM     LOG [MigrateWorkflowCodeStepsCommand] Running MigrateWorkflowCodeStepsCommand for workspace 7a36809e-0067-4bdb-a8d9-42b3093c23f0
[Nest] 99  - 02/19/2026, 10:44:04 AM    WARN [UpgradeCommand] Error in workspace 7a36809e-0067-4bdb-a8d9-42b3093c23f0: ENOENT: no such file or directory, scandir '/app/packages/twenty-server/.local-storage/workspace-7a36809e-0067-4bdb-a8d9-42b3093c23f0/built-function/80e7ae27-c31c-4bc4-9756-c699d5330ee3/1'
[Nest] 99  - 02/19/2026, 10:44:04 AM   ERROR [UpgradeCommand] Error in workspace 7a36809e-0067-4bdb-a8d9-42b3093c23f0: ENOENT: no such file or directory, scandir '/app/packages/twenty-server/.local-storage/workspace-7a36809e-0067-4bdb-a8d9-42b3093c23f0/built-function/80e7ae27-c31c-4bc4-9756-c699d5330ee3/1'
[Nest] 99  - 02/19/2026, 10:44:04 AM     LOG [UpgradeCommand] Command completed!
[Nest] 99  - 02/19/2026, 10:44:04 AM   ERROR [UpgradeCommand] undefined

After that, twenty server just crash (the docker container stops).

Technical inputs

Some information that may be useful (or not at all):

  • Twenty is self-hosted, using Docker compose.
  • We had enabled the Dashboard feature in beta in version v1.14
  • I just successively upgraded twenty from v1.14, upgrading from successive version (v1.14 -> v1.15, v1.15 -> v1.16) without noticing any errors just before trying to upgrade to v1.17.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    πŸ”– Planned

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions