Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. Twenty
  3. Twenty CRM update on Cloudron fails – database schema mismatch (missing column)

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

Scheduled Pinned Locked Moved Twenty
4 Posts 2 Posters 26 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    david.opalia
    wrote last edited by james
    #1

    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.

    1 Reply Last reply
    1
    • jamesJ Offline
      jamesJ Offline
      james
      Staff
      wrote last edited by
      #2

      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?

      1 Reply Last reply
      1
      • D Offline
        D Offline
        david.opalia
        wrote last edited by
        #3

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

        jamesJ 1 Reply Last reply
        0
        • D 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?

          jamesJ Offline
          jamesJ Offline
          james
          Staff
          wrote last edited by
          #4

          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.

          1 Reply Last reply
          1

          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
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Bookmarks
          • Search