Twenty CRM update on Cloudron fails – database schema mismatch (missing column)
-
Error logs
QueryFailedError: column core.workspace.useRecommendedModels does not exist code: '42703' routine: 'errorMissingColumn'This happens during a query when checking user existence (CheckUserExists).
What I understand
It looks like the application expects new fields in the core.workspace table, but the database schema was not updated accordingly.
What I tried
I manually added one missing column:
ALTER TABLE core.workspace ADD COLUMN "enabledAiModelIds" jsonb;But the app still fails due to another missing column:
useRecommendedModelsAdditional issue
I tried to run migrations manually:
npm run typeorm migration:runBut the script does not exist.
-
@james yes, it works.
After investigation, the issue appears to be related to a version gap:
Current instance version: 1.18
Upgrade attempted directly to 1.21
The system requires at least 1.20 for workspace migrations to proceedAs a result, at least one workspace (my unique workspace) seems to still be at a version below 1.20 (1.18 here), which blocks the global upgrade process.
@nebulon @james Going forward, could we consider performing updates step-by-step to avoid this kind of issue?
-
@james yes, it works.
After investigation, the issue appears to be related to a version gap:
Current instance version: 1.18
Upgrade attempted directly to 1.21
The system requires at least 1.20 for workspace migrations to proceedAs a result, at least one workspace (my unique workspace) seems to still be at a version below 1.20 (1.18 here), which blocks the global upgrade process.
@nebulon @james Going forward, could we consider performing updates step-by-step to avoid this kind of issue?
Hello @david.opalia
@nebulon @james Going forward, could we consider performing updates step-by-step to avoid this kind of issue?
This is the case for all apps that are not marked as unstable.
Unstable apps are subjected to changes that can break the app. Like you have experienced here.
We do this with unstable apps so we can get them into a stable state as fast as possible.
Since there can be major issues with previous versions of an unstable app, a breaking version that gets us faster to a stable release is sometimes more efficient than handling the issues of the previous version into the next version and so on.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login