Crosp Posts - Answer Overflow

Crosp

•Created by Crosp on 2/18/2025 in #❓︱help

Upgrade 0.22 -> 0.23

Hi, I'm facing an issue during the upgrade from a 0.22 to 0.23 instance. Following upgrade guide, during the yarn comand:prod upgrade-0.23 command:

[Nest] 284  - 02/18/2025, 3:32:47 PM     LOG [UpdateActivitiesCommand] Running command on workspace xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx failed
[Nest] 284  - 02/18/2025, 3:32:47 PM   ERROR [UpdateActivitiesCommand] Migration failed for workspace xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx: No metadata for "task" was found., EntityMetadataNotFoundError: No metadata for "task" was found.
    at WorkspaceDataSource.getMetadata (/app/node_modules/typeorm/data-source/DataSource.js:304:19)
    at get metadata [as metadata] (/app/node_modules/typeorm/repository/Repository.js:15:40)
    at WorkspaceRepository.create (/app/node_modules/typeorm/repository/Repository.js:52:41)
    at updateActivities (/app/packages/twenty-server/dist/src/database/commands/upgrade-version/0-23/0-23-update-activities.command.js:110:49)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async UpdateActivitiesCommand.executeWithQueryRunner (/app/packages/twenty-server/dist/src/database/commands/upgrade-version/0-23/0-23-update-activities.command.js:279:21)
    at async UpdateActivitiesCommand.sharedBoilerplate (/app/packages/twenty-server/dist/src/database/commands/upgrade-version/0-23/0-23-update-activities.command.js:257:21)
    at async UpgradeTo0_23Command.run (/app/packages/twenty-server/dist/src/database/commands/upgrade-version/0-23/0-23-upgrade-version.command.js:43:9)
    at async Command.<anonymous> (/app/node_modules/nest-commander/src/command-runner.service.js:156:24)
    at async Command.parseAsync (/app/node_modules/commander/lib/command.js:936:5)

[Nest] 284  - 02/18/2025, 3:32:47 PM     LOG [UpdateActivitiesCommand] Running command on workspace xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx failed
[Nest] 284  - 02/18/2025, 3:32:47 PM   ERROR [UpdateActivitiesCommand] Migration failed for workspace xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx: No metadata for "task" was found., EntityMetadataNotFoundError: No metadata for "task" was found.
    at WorkspaceDataSource.getMetadata (/app/node_modules/typeorm/data-source/DataSource.js:304:19)
    at get metadata [as metadata] (/app/node_modules/typeorm/repository/Repository.js:15:40)
    at WorkspaceRepository.create (/app/node_modules/typeorm/repository/Repository.js:52:41)
    at updateActivities (/app/packages/twenty-server/dist/src/database/commands/upgrade-version/0-23/0-23-update-activities.command.js:110:49)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async UpdateActivitiesCommand.executeWithQueryRunner (/app/packages/twenty-server/dist/src/database/commands/upgrade-version/0-23/0-23-update-activities.command.js:279:21)
    at async UpdateActivitiesCommand.sharedBoilerplate (/app/packages/twenty-server/dist/src/database/commands/upgrade-version/0-23/0-23-update-activities.command.js:257:21)
    at async UpgradeTo0_23Command.run (/app/packages/twenty-server/dist/src/database/commands/upgrade-version/0-23/0-23-upgrade-version.command.js:43:9)
    at async Command.<anonymous> (/app/node_modules/nest-commander/src/command-runner.service.js:156:24)
    at async Command.parseAsync (/app/node_modules/commander/lib/command.js:936:5)

This seems to happen each time, and all notes are missing after the upgrade. If someone can help, this would be very usefull. Thanks !

6 replies

TTwenty

•Created by Crosp on 2/5/2025 in #❓︱help

Migration from 0.33.0 to 0.34.0 causes errors

12 replies

TTwenty

•Created by Crosp on 10/31/2024 in #❓︱help

Install docker-zapier into a Twenty docker instance

Hi everyone, I manage a twenty docker instance, and I would like to install twenty-zapier package into. From your zapier-app documentation page https://twenty.com/developers/section/backend-development/zapier, I can see the setup is based on a yarn install triggered from packages/twenty-zapier directory. Can you confirm please that this is the only existing method, even for a zapier docker instance ? Because I guess I would need to do it again when my docker container get killed. Or maybe for the moment the Zapier App setup is not designed for twenty docker instances ? Regards, and thanks for your work !

9 replies

Gaming

Programming