Upgrade not Possible: Manifest Unknown | Twenty | Page 1

unreal kayak Oct 28, 2025, 3:49 PM

#

I'm self-hosting and tried to update v 1.7.0 and 1.8.0 (currently on 1.6.7), but I keep getting this error:

2025-Oct-28 15:46:40.269688
server Error manifest for twentycrm/twenty:v1.7.0 not found: manifest unknown: manifest unknown
2025-Oct-28 15:46:40.269688
worker  Interrupted
2025-Oct-28 15:46:40.269688
Error response from daemon: manifest for twentycrm/twenty:v1.7.0 not found: manifest unknown: manifest unknown
2025-Oct-28 15:46:40.269688
exit status 1

What's causing this and what can I do?

polar pond Oct 28, 2025, 3:49 PM

#

Hey @unreal kayak Please upgrade to latest 1.7 patch version

#

Please also share the whole logs

unreal kayak Oct 28, 2025, 3:51 PM

#

polar pond Please also share the whole logs

Using Coolify and these are all the logs I am getting on deploying:

2025-Oct-28 15:46:39.007594
server Pulling
2025-Oct-28 15:46:40.227039
server Error manifest for twentycrm/twenty:v1.7.0 not found: manifest unknown: manifest unknown
2025-Oct-28 15:46:40.230939
worker  Interrupted
2025-Oct-28 15:46:40.230939
Error response from daemon: manifest for twentycrm/twenty:v1.7.0 not found: manifest unknown: manifest unknown
2025-Oct-28 15:46:40.234144
exit status 1
2025-Oct-28 15:46:40.260489
Oops something is not okay, are you okay? 😢
2025-Oct-28 15:46:40.269688
worker Pulling
2025-Oct-28 15:46:40.269688
server Pulling
2025-Oct-28 15:46:40.269688
server Error manifest for twentycrm/twenty:v1.7.0 not found: manifest unknown: manifest unknown
2025-Oct-28 15:46:40.269688
worker  Interrupted
2025-Oct-28 15:46:40.269688
Error response from daemon: manifest for twentycrm/twenty:v1.7.0 not found: manifest unknown: manifest unknown
2025-Oct-28 15:46:40.269688
exit status 1

polar pond Oct 28, 2025, 3:51 PM

#

That's becasue 1.7.0 does not exist

#

Please consunme the 1.7 mirror patch agnostical

#

from docker hub

unreal kayak Oct 28, 2025, 3:52 PM

#

polar pond Hey <@1314107742465691690> Please upgrade to latest 1.7 patch version

Where do I find this?

#

ah

polar pond Oct 28, 2025, 3:52 PM

#

https://hub.docker.com/r/twentycrm/twenty/tags

#

Please review your workspace version in database before and after the upgrade

unreal kayak Oct 28, 2025, 3:53 PM

#

That's inconvenient. I cannot switch installation methods. I commited to docker compose via Coolify and using a Docker Image basically forces me to create a new app and re-invite all users etc.

polar pond Oct 28, 2025, 3:54 PM

#

Coolify consumes the docker hub images under the hood

unreal kayak Oct 28, 2025, 3:55 PM

#

Interesting. Not that tech-savvy. How can I use the patch version without creating a new app?

#

Can I use a particular tag?

polar pond Oct 28, 2025, 3:58 PM

#

I'm not familiar with coolify
You should be able to update the TAG version of your .env

#

To be pointing on 1.7 instead of 1.7.0

#

( the same way you've followed to achieve to the point you're atm => eg consuming 1.7.0 )

unreal kayak Oct 28, 2025, 3:58 PM

#

That's easy enough. I'll try 1.7

unreal kayak Oct 28, 2025, 4:04 PM

#

unreal kayak That's easy enough. I'll try 1.7

That worked. Thanks for the help. Can I now switch to 1.7.0 and 1.8.0?

polar pond Oct 28, 2025, 4:05 PM

#

Please try avoiding consuming patched version, stay abstract and keep to consuming 1.7 and 1.8

#

Please double check that your workspace version in database is correct

unreal kayak Oct 28, 2025, 4:09 PM

#

My workspace version actually show 1.7.7 instead of 1.7. But just for my understanding: The production-ready version always 2 digits and 3 digits is the "patched" version?

polar pond Oct 28, 2025, 4:12 PM

#

When you consume the patch agnostical it will find the latest 1.7 version

#

So everything's good here

#

The upgrade was successful

#

The versioning follows semver
major.minor.patch

Semantic Versioning

Semantic Versioning 2.0.0

Semantic Versioning spec and website

#

You can attempt to 1.8 upgrade if you want to

unreal kayak Oct 28, 2025, 4:21 PM

#

polar pond You can attempt to 1.8 upgrade if you want to

OK, that broke things unfortuntely. My logs:
Server:

...
2025-10-28T16:17:09.181579499Z       position: '490',
2025-10-28T16:17:09.181582215Z       internalPosition: undefined,
2025-10-28T16:17:09.181584840Z       internalQuery: undefined,
2025-10-28T16:17:09.181587445Z       where: undefined,
2025-10-28T16:17:09.181590109Z       schema: undefined,
2025-10-28T16:17:09.181592664Z       table: undefined,
2025-10-28T16:17:09.181595189Z       column: undefined,
2025-10-28T16:17:09.181597734Z       dataType: undefined,
2025-10-28T16:17:09.181600338Z       constraint: undefined,
2025-10-28T16:17:09.181602903Z       file: 'parse_relation.c',
2025-10-28T16:17:09.181605468Z       line: '3722',
2025-10-28T16:17:09.181608103Z       routine: 'errorMissingColumn'
2025-10-28T16:17:09.181610867Z     }
2025-10-28T16:17:09.181613482Z   ]

Worker:

...
2025-10-28T16:17:07.742124271Z       file: 'parse_relation.c',
2025-10-28T16:17:07.742126897Z       line: '3722',
2025-10-28T16:17:07.742129552Z       routine: 'errorMissingColumn'
2025-10-28T16:17:07.742132146Z     }
2025-10-28T16:17:07.742134680Z   ]
2025-10-28T16:17:07.752058028Z [Nest] 34  - 10/28/2025, 4:17:07 PM     LOG ;5;3m[BullMQDriver] Processing job repeat:CronTriggerCronJob:1761668220000 with name CronTriggerCronJob on queue cron-queue
2025-10-28T16:17:07.768507478Z [Nest] 34  - 10/28/2025, 4:17:07 PM     LOG ;5;3m[BullMQDriver] Job repeat:CronTriggerCronJob:1761668220000 with name CronTriggerCronJob processed on queue cron-queue in 16.37ms

Does this require a ticket on Github or it it a know issue with a quick fix?

polar pond Oct 28, 2025, 4:21 PM

#

Please share the whole logs seems to be truncated

unreal kayak Oct 28, 2025, 4:22 PM

#

They are due to message constraints

#

Server

📎 message.txt

#

Worker

📎 message.txt

polar pond Oct 28, 2025, 4:27 PM

#

My workspace version actually show 1.7.7 instead of 1.7.
How are you viewing this please ?

#

Seems like you're missing a previous migration

unreal kayak Oct 28, 2025, 4:28 PM

#

polar pond > My workspace version actually show 1.7.7 instead of 1.7. How are you viewing ...

That changed when I deployed 1.7. It was 1.6.7 before that. Both values were identical

polar pond Oct 28, 2025, 4:29 PM

#

Where do you read the info please

unreal kayak Oct 28, 2025, 4:29 PM

#

In the UI

polar pond Oct 28, 2025, 4:29 PM

#

That's why, please try inspecting your database at core.workspace.version
Unfortunately, not very intuitive they are not the same info

unreal kayak Oct 28, 2025, 4:46 PM

#

polar pond That's why, please try inspecting your database at `core.workspace.version` Unfo...

Took me a second to get it: 1.6.7

polar pond Oct 28, 2025, 4:47 PM

#

Ok the upgrade failed please inspect error I suspect the same as https://discord.com/channels/1130383047699738754/1430251005534011523 please refer to this channel in order to resolve the issue

unreal kayak Oct 28, 2025, 5:06 PM

#

polar pond Ok the upgrade failed please inspect error I suspect the same as https://discord...

So I went back to 1.6.7 and upgraded to 1.7. Here's what I'm seeing: No errors in my deployment or runtime logs of server, worker or db, but this line here is weird

2025-10-28T16:57:33.690815763Z Database setup and migrations are disabled, skipping...
2025-10-28T16:57:33.690871107Z Cron job registration is disabled, skipping...
2025-10-28T16:57:44.070987576Z [Nest] 34  - 10/28/2025, 4:57:44 PM     LOG ;5;3m[NestFactory] Starting Nest application...

My enviroment variables are actually set to this:

DISABLE_CRON_JOBS_REGISTRATION=false
DISABLE_DB_MIGRATIONS=false

It's a "double negation" meaning I want to enable cron jobs and migrations. COuld this be the issue?

polar pond Oct 28, 2025, 5:07 PM

#

You should not have to touch to that

#

Please share your whole twenty-server logs

#

Upgrade command is run at the very first steps of your twenty-server bootstrap

unreal kayak Oct 28, 2025, 5:09 PM

#

Server runtime

📎 message.txt

polar pond Oct 28, 2025, 5:10 PM

#

8T16:57:08.922460232Z [Nest] 57  - 10/28/2025, 4:57:08 PM   ERROR ;5;3m[WorkspaceSyncMetadataService] EntityPropertyNotFoundError: Property "createHandoffFromDefaultAgent" was not found in "AgentEntity". Make sure your query is correct.
2025-10-28T16:57:09.839693536Z [Nest] 57  - 10/28/2025, 4:57:09 PM    WARN ;5;3m[UpgradeCommand] Error in workspace 2fb6fdd2-2d9e-4726-8dd1-780489cac97d: Property "createHandoffFromDefaultAgent" was not found in "AgentEntity". Make sure your query is correct.
2025-10-28T16:57:09.840024404Z PromiseMemoizer Event: A WorkspaceDataSource for workspace 2fb6fdd2-2d9e-4726-8dd1-780489cac97d is being cleared. Actual pool closure managed by PgPoolSharedService. Not calling dataSource.destroy().
2025-10-28T16:57:09.840310529Z [Nest] 57  - 10/28/2025, 4:57:09 PM   ERROR ;5;3m[UpgradeCommand] Error in workspace 2fb6fdd2-2d9e-4726-8dd1-780489cac97d: Property "createHandoffFromDefaultAgent" was not found in "AgentEntity". Make sure your query is correct.
2025-10-28T16:57:09.840325968Z [Nest] 57  - 10/28/2025, 4:57:09 PM   ERROR ;5;3m[UpgradeCommand] undefined
2025-10-28T16:57:09.840498090Z [Nest] 57  - 10/28/2025, 4:57:09 PM     LOG ;5;3m[UpgradeCommand] Command completed!

#

Duplicated of https://discord.com/channels/1130383047699738754/1430251005534011523

#

Hey @graceful dock do you have more information regarding the createHandoffFromDefaultAgent introduction
Could this migration have been introduced in a patch version of twenty ?

#

@unreal kayak I've removed the messages that might have contained private information about your coolify instance

#

createHandoffFromDefaultAgent seems to be quite hacky in the way it has been associated with the agent definition
The sync metadata seems to be expecting a column for it whereas it just contextual metadata for standard agent creation

#

@graceful dock createHandoffFromDefaultAgent does not seem to be consumed in the end or I'm misunderstanding something here

#

My guess would be that:

createHandoffFromDefaultAgent: true, has been introduced 4 weeks ago in standard roles declaration
but extraction of the given field has been introduced two weeks ago

export const transformStandardAgentDefinitionToFlatAgent = (
  standardAgentDefinition: StandardAgentDefinition,
  workspaceId: string,
): FlatAgent => {
  const {
    createHandoffFromDefaultAgent: _createHandoffFromDefaultAgent,
    standardRoleId: _standardRoleId,
    ...agentData
  } = standardAgentDefinition;

#

There's a time lapse where some selft hosters might have been able to introduce roles with the data while proceeding to a sync metadata ( might also occur in production too )

// packages/twenty-server/src/engine/workspace-manager/workspace-sync-metadata/services/workspace-sync-agent.service.ts
    const targetStandardAgents = this.standardAgentFactory.create(
      standardAgentDefinitions,
      context,
      existingStandardAgentEntities,
    );

#

But overall this does not seem to be a consumed property at all within the codebase if it's not even declare the role entity

unreal kayak Oct 30, 2025, 8:34 AM

#

So is there a solution for this issue?

polar pond Oct 30, 2025, 8:47 AM

#

Could you please dm me all your agent in database located at core.agent ? @unreal kayak

#Upgrade not Possible: Manifest Unknown