[self hosted] broken after upgrade to 1.3.0

Hi. I am getting this issue and I am unsure how to fix this. Maybe someone can help me? On workspace load, I am getting error in an API call: Request
{"operationName":"FindManyFavoriteFolders","variables":{},"query":"query FindManyFavoriteFolders($filter: FavoriteFolderFilterInput, $orderBy: [FavoriteFolderOrderByInput], $lastCursor: String, $limit: Int) {\n favoriteFolders(\n filter: $filter\n orderBy: $orderBy\n first: $limit\n after: $lastCursor\n ) {\n edges {\n node {\n __typename\n createdAt\n deletedAt\n id\n name\n position\n updatedAt\n }\n cursor\n __typename\n }\n pageInfo {\n hasNextPage\n hasPreviousPage\n startCursor\n endCursor\n __typename\n }\n totalCount\n __typename\n }\n}"}
{"operationName":"FindManyFavoriteFolders","variables":{},"query":"query FindManyFavoriteFolders($filter: FavoriteFolderFilterInput, $orderBy: [FavoriteFolderOrderByInput], $lastCursor: String, $limit: Int) {\n favoriteFolders(\n filter: $filter\n orderBy: $orderBy\n first: $limit\n after: $lastCursor\n ) {\n edges {\n node {\n __typename\n createdAt\n deletedAt\n id\n name\n position\n updatedAt\n }\n cursor\n __typename\n }\n pageInfo {\n hasNextPage\n hasPreviousPage\n startCursor\n endCursor\n __typename\n }\n totalCount\n __typename\n }\n}"}
Response
{
"errors": [
{
"message": "Unable to merge GraphQL type \"Query\": Field \"apiKeys\" already defined with a different type. Declared as \"ApiKey\", but you tried to override with \"ApiKeyConnection\""
}
]
}
{
"errors": [
{
"message": "Unable to merge GraphQL type \"Query\": Field \"apiKeys\" already defined with a different type. Declared as \"ApiKey\", but you tried to override with \"ApiKeyConnection\""
}
]
}
It seems like a graphql schema migration issue but I am unable to figure out a fix. I also get the same error in FindManyFavorites query
12 Replies
charles
charles4d ago
@hassaanz what version of Twenty are your running and what do you see in your core.workspace table in version column?
hassaanz
hassaanzOP4d ago
I just upgraded to 1.4.0. Let me have a look at the db table and get back
charles
charles4d ago
it seems that something went wrong while upgrading to 1.3.0 this is an error linked to 1.3.0
hassaanz
hassaanzOP4d ago
Yes. I got the error when I upgraded to 1.3.0
charles
charles4d ago
ok, let's go back to 1.3.1 first 🙂 currently, we still need to go through each version and make sure it's working fine everytime what version do you originally come from (before starting upgrading?)
hassaanz
hassaanzOP4d ago
oh... I just did a docker pull to latest I think I missed a few migrations I am not sure. I think I was on 1.2.0
charles
charles4d ago
ok !
hassaanz
hassaanzOP4d ago
Do you suggest going back to 1.3.1 and then upgrade step by step?
charles
charles4d ago
This will be supported in October for now you need to put 1.3 in your docker-compose / .env docker compose up -d make sure it's working then you can move to 1.4
hassaanz
hassaanzOP4d ago
Yup. Let me try it out
charles
charles4d ago
I recommend not leaving "latest" in your .env, it's a bit dangerous for a production setup
hassaanz
hassaanzOP4d ago
Thanks for the tip Is it possible I can contribute to this somehow? I belive this is related to DB migrations. Maybe a github issue I can pick up? I am going back to 1.3.0 and report back So I went down to 1.3.0 and the issue was still there. So I went down to 1.2.0 and was able to fix this. Now I am going up incrementally. Is there a difference between 1.3.0 and 1.3? These are two different tags on docker images

Did you find this page helpful?