Twenty•2mo ago

After upgrading to 1.6.0 nothing is accessible

The response of a lot of queries is:

{
    "errors": [
        {
            "message": "No role found for userWorkspace",
            "extensions": {
                "code": "INTERNAL_SERVER_ERROR",
                "userFriendlyMessage": "An error occurred."
            }
        }
    ],
    "data": {
        "favoriteFolders": null
    }
}

{
    "errors": [
        {
            "message": "No role found for userWorkspace",
            "extensions": {
                "code": "INTERNAL_SERVER_ERROR",
                "userFriendlyMessage": "An error occurred."
            }
        }
    ],
    "data": {
        "favoriteFolders": null
    }
}

22 Replies

Prastoin•2mo ago

Please try clearing cache Yarn command:prod cache:flush

kyoma•2mo ago

getting the same error tried to clear cache, delete postgres and redis docker image and followed the local setup step by step

Prastoin•2mo ago

What's your workspace version in database Core.workspace.version

kyoma•2mo ago

[null]

Prastoin•2mo ago

Are you building your own twenty image ?

kyoma•2mo ago

no, I just ran make postgres-on-docker

Prastoin•2mo ago

I'm not sure to understand If you consume one of the official twenty image your workspace version cannot be null

kyoma•2mo ago

🤷 I just followed the local setup https://twenty.com/developers/local-setup for WSL with docker

Twenty - Local Setup

The guide for contributors (or curious developers) who want to run Twenty locally (on laptop, PC...)

fluffysheap•2mo ago

FWIW I'm having the same issue, but it happened upgrading from 1.7.3 to 1.7.6 Which isn't even supposed to be a database change

kyoma•2mo ago

and both Apple and YC workspace have [null] version

fluffysheap•2mo ago

No amount of yarn jiggery-pokery helps I will attach a much more thorough log

fluffysheap•2mo ago

upgrade-173to176.log

Prastoin•2mo ago

So you're not deploying a version of twenty such as op ( unless I'm mistaken ) but rather having a trouble issue with local env Please crête a dedicated help thred It's normal to have a null version in local You can try running npx nx database:reset too There's no need to run any command between patch version Please clear you cache

DaanOP•2mo ago

I'm currently on version 1.7.6, but the issue persists. Using the docker compose stack. Also tried clearing cache, manually clearing redis cache without luck

Prastoin•2mo ago

Hey @Daan what's your workspace version in db please

Jamsian•2mo ago

Same issue. It looks like metadata:permissions:user-workspace-role-map cache key is not setting on the current master, or refreshed from DB. checking out to v1.6.0, everything works correctly.

DaanOP•2mo ago

The workspace version, shows also 1.7.6 and metadata version 39

fluffysheap•2mo ago

As I said already no amount of fussing with yarn helps

fjcero•2mo ago

Same here, having this logs after doing manual migration Migration "ActivateUnaccentExtension1758117800000" failed, error: cannot change name of input parameter "input" I'm using 1.6.7 because of the comment on Github Tag

fluffysheap•2mo ago

That might be a different problem

fjcero•2mo ago

ah well, everything works well in 1.5, whenever I want to migrate to 1.6 I start having issues with migrations nvm, fixed it by forcing migrations

DaanOP•2mo ago

This is fixed in version 1.7.7, thanks @prastoin!

Gaming

Programming

After upgrading to 1.6.0 nothing is accessible

Did you find this page helpful?