I have an installation where the tag in docker has been incremented up to v1.18 but the workspace is still reporting as v1.15. I guess the database upgrades weren't done correctly for v1.16, v1.17 and v1.18. How screwed am I?
#Workspace and app versions don't match. I'm dumb.
wary thistle
rough mist
Hello there, depends if you're manually run the database migrations or not
Could you please share your workspace._typeorm_migrations values ?
If you've forced the database migration you will have to restart from scratch exporting data as csv and re-configuring your data model etc
If not you will have to downgrade to 1.16 to determine what's blocking your to upgrade from 1.15
wary thistle
I have spent a few hours trying to migrate the db with no success. This is above my knowledge level. I do have a backup I can restore where I believe no db upgrade/migration was ever run. I think my colleague was just upping the tag in docker as new versions came out.
It sounds like starting that point may be the best thing for me?
wary thistle
If I rollback to my backup and set the tag to v1.16 I get these errors in the logs when booting:
Looks like something about standardid was migrated through some mechanism other than the upgrade command?
wary thistle
Could you please share your workspace._typeorm_migrations values ?
As requested
Also this is probably obvious to people how know what they're doing but if I run the upgrade command from the article I see for upgrading with tag is set to v1.16 I get this:
[Nest] 460 - 04/28/2026, 7:22:33 PM LOG [DatabaseConfigDriver] [INIT] Loading initial config variables from database
[Nest] 460 - 04/28/2026, 7:22:33 PM LOG [DatabaseConfigDriver] [INIT] Config variables loaded: 9 values found in DB, 61 falling to env vars/defaults
error: unknown command 'upgrade:status'
[Nest] 460 - 04/28/2026, 7:22:33 PM ERROR [CommanderError] error: unknown command 'upgrade:status'
Exception Captured
undefined
[
CommanderError: error: unknown command 'upgrade:status'
at Command._exit (/app/node_modules/nest-commander/node_modules/commander/lib/command.js:461:26)
at Command.error (/app/node_modules/nest-commander/node_modules/commander/lib/command.js:1604:10)
at Command.unknownCommand (/app/node_modules/nest-commander/node_modules/commander/lib/command.js:1795:10)
at Command._parseCommand (/app/node_modules/nest-commander/node_modules/commander/lib/command.js:1317:14)
at Command.parseAsync (/app/node_modules/nest-commander/node_modules/commander/lib/command.js:936:16)
at CommandRunnerService.run (/app/node_modules/nest-commander/src/command-runner.service.js:211:14)
at CommandFactory.runApplication (/app/node_modules/nest-commander/src/command.factory.js:41:22)
at bootstrap (/app/packages/twenty-server/dist/command/command.js:33:41)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5) {
code: 'commander.unknownCommand',
exitCode: 1,
nestedError: undefined
}
]
rough mist
If I rollback to my backup and set the tag to v1.16 I get these errors in the lo...
Sounds like a corrupted schema, standard id has been deprecated and not introduced in later twenty version
Could you please share your core._typeorm_migrations rows ?
rough mist
Also this is probably obvious to people how know what they're doing but if I run...
That's because this command has been introduced starting +1.22
You need to inspect your twenty-server logs and look at the core.workspace.version to know where your workspace is at exactly
wary thistle
As requested
Is this not what you mean by core._typeorm_migrations rows ?
rough mist
Is this not what you mean by `core._typeorm_migrations` rows ?
my bad
checking
MakeRemainingEntitiesUniversalIdentifierAndApplicationIdNotNullable1768916632478 has been introduced in v1.15 so you're good to go
Instance isn't corrupted here
Could you please share the whole twenty-server logs after restarting ?
It should contain an upgrade error
wary thistle
2026-04-28T19:30:37.365575795Z [Nest] 92 - 04/28/2026, 7:30:37 PM LOG [UpgradeCommand] Initialized upgrade context with:
2026-04-28T19:30:37.365585623Z - currentVersion (migrating to): 1.18.1
2026-04-28T19:30:37.365588288Z - fromWorkspaceVersion: 1.17.0
2026-04-28T19:30:37.365590272Z - 9 commands
2026-04-28T19:30:37.369946635Z [Nest] 92 - 04/28/2026, 7:30:37 PM ERROR [UpgradeCommand] Error in workspace 291c15fb-9600-4ac5-a05c-b3adf857faee: Unable to run the upgrade command. Aborting the upgrade process.
2026-04-28T19:30:37.369980780Z Please ensure that all workspaces are on at least the previous minor version (1.17.0).
2026-04-28T19:30:37.369985319Z If any workspaces are not on the previous minor version, roll back to that version and run the upgrade command again.
2026-04-28T19:30:37.370043809Z [Nest] 92 - 04/28/2026, 7:30:37 PM ERROR [UpgradeCommand] undefined
2026-04-28T19:30:37.370073745Z [Nest] 92 - 04/28/2026, 7:30:37 PM LOG [UpgradeCommand] Command compl
First 5 minutes.
wary thistle
@rough mist - does that log give you any insight into what my path forward should be?
wary thistle
I had each minor version installed at one point. I went v1.15 to v1.16 to v1.17 to v1.18 but the workspace got stuck at v1.15 clearly. At this point I don't think I can roll back to v1.16 to see what went wrong, can I?
wary thistle
Bump. Still need help with this if anyone can help. I can pay.
rough mist
Hey there
I had each minor version installed at one point. I went v1.15 to v1.16 to v1.17 to v1.18 but the workspace got stuck at v1.15 clearly. At this point I don't think I can roll back to v1.16 to see what went wrong, can I?
Please restore a v15 backup or downgrade safe up to there by just changing your tag to v1.15
from the moment you haven't manually forced typeorm migrations to run your instance hasn't been corrupted
We have something to handle with your data in 1.15
wary thistle
I can't roll back to v1.15 - I get errors about standardId
I think the upgrade to v1.16 moved me off standardid but didn't finish the migrations and now I'm in a weird limbo
wary thistle
A backup of what? Tons of data has been added to the db since the backup from v1.15