T
Twenty•4mo ago
Jonas L. | Minecoll_YT

Database upgrade error

Hello! I just upgraded my twenty from v0.51.0 to v0.52.7 and then run the two commands to upgrade the db. The first one ran without any visible errors but the second one throws and error. But the workspaces seems to be working fine 
[Nest] 288  - 05/29/2025, 6:20:45 PM     LOG [UpgradeCommand]  Upgrading workspace 5511aa2d-b268-493d-aa9b-250a2b76ef4a 1/1
[Nest] 288  - 05/29/2025, 6:20:45 PM    WARN [UpgradeCommand] Error in workspace 5511aa2d-b268-493d-aa9b-250a2b76ef4a: WORKSPACE_VERSION_MISSMATCH Upgrade for workspace 5511aa2d-b268-493d-aa9b-250a2b76ef4a failed as its version is beneath fromWorkspaceVersion=0.51.0
[Nest] 288  - 05/29/2025, 6:20:45 PM   ERROR [UpgradeCommand] Error in workspace 5511aa2d-b268-493d-aa9b-250a2b76ef4a: WORKSPACE_VERSION_MISSMATCH Upgrade for workspace 5511aa2d-b268-493d-aa9b-250a2b76ef4a failed as its version is beneath fromWorkspaceVersion=0.51.0
[Nest] 288  - 05/29/2025, 6:20:45 PM   ERROR [UpgradeCommand] undefined
[Nest] 288  - 05/29/2025, 6:20:45 PM     LOG [UpgradeCommand] Command completed
[Nest] 288  - 05/29/2025, 6:20:45 PM     LOG [UpgradeCommand]  Upgrading workspace 5511aa2d-b268-493d-aa9b-250a2b76ef4a 1/1
[Nest] 288  - 05/29/2025, 6:20:45 PM    WARN [UpgradeCommand] Error in workspace 5511aa2d-b268-493d-aa9b-250a2b76ef4a: WORKSPACE_VERSION_MISSMATCH Upgrade for workspace 5511aa2d-b268-493d-aa9b-250a2b76ef4a failed as its version is beneath fromWorkspaceVersion=0.51.0
[Nest] 288  - 05/29/2025, 6:20:45 PM   ERROR [UpgradeCommand] Error in workspace 5511aa2d-b268-493d-aa9b-250a2b76ef4a: WORKSPACE_VERSION_MISSMATCH Upgrade for workspace 5511aa2d-b268-493d-aa9b-250a2b76ef4a failed as its version is beneath fromWorkspaceVersion=0.51.0
[Nest] 288  - 05/29/2025, 6:20:45 PM   ERROR [UpgradeCommand] undefined
[Nest] 288  - 05/29/2025, 6:20:45 PM     LOG [UpgradeCommand] Command completed
1 Reply
Jonas L. | Minecoll_YT
Jonas L. | Minecoll_YTOP•4mo ago
I just checked the version value in the core.workspace table and its at 0.50.5. So it seems like I missed upgrading the table when I updated to 0.51.0v. What would be the best way to resolve this issue? (Also if someone had forgotten to make a backup of the database... only theoretically of course...) Okay, just editing the version inside the db seems to have fixed the problem without any issue

Did you find this page helpful?