Twenty CRM update on Cloudron fails – database schema mismatch (missing column)

[david.opalia]

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:

useRecommendedModels

Additional issue

I tried to run migrations manually:

npm run typeorm migration:run

But the script does not exist.

[james]

Hello @david.opalia
The app is still marked as unstable.
We have recently made a big change to the app.
Could you please try to uninstall the app and install it again?

[david.opalia]

@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 proceed

As 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]

Hello @david.opalia

@david.opalia said:

@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.

[admin 0]

No chance here to migrate? Just trying to avoid re-configuring all objects and migrate all my data.

[james]

Hello @admin-0
Currently no.
But, let me get back to you on that.
We might be able to push the other version for 1.20 as well to avoid this struggle.

[james]

Hello @admin-0

After some investigation the effort would be too high for an unstable app.
Thus, unfortunately we can't provide support.
You will have to reinstall the app.

[nebulon]

But it is valuable information at least that apparently the app needs to be updated one version after the other.

[JLX89]

I'm attempting to login to Twenty, but seeing a server error occurred and unable to login. I've sanitized the logs and provided them at: https://paste.cloudron.io/moludibicu.sql

Any thoughts?

[james]

Hello @jlx89
Please see the solution above.
Or the issue is related to https://forum.cloudron.io/post/123360 which also has a fix.

[david.opalia]

@nebulon

The documentation say :
"Cross-version upgrades (v1.22+)
Starting from v1.22, Twenty supports cross-version upgrades. You can jump directly from any supported version to the latest release without stepping through each intermediate version. For example, upgrading from v1.22 straight to v2.0 is fully supported."

So I think it's ok for now.