Upgrading to v1.1.1 broke workflows
Congrats on the new release!
I self host and updated from v1.0.3 to v1.1.1 and its working lovely, except my workflows (that previously ran smoothly) no longer run. I get the error
EntityPropertyNotFoundError: Property "state" was not found in "workflowRun". Make sure your query is correct. when i try and run them.
So i tried manually running yarn command:prod upgrade in my worker docker instance (maybe a bad idea because I though i read somehwere thats no longer needed) but it says "yarn command:prod upgrade". so i tried running yarn command:prod upgrade:1-1:migrate-workflow-run-state, but it throws Error in workspace 6e278d07-a88a-45d3-86c9-daea30a9b0e5: Property "state" was not found in "workflowRun"
I see that others have workflows working on v.1.1, so I suspect I have done something wrong, or its an issue because I have been upgrading steadily for many versions and possibly missed a step in the past.
Any suggestions on what i might have done wrong during my upgrade (simply bumping the docker-compose version number and pull//up)? And how I might fix the current issue with the workflows?
Thanks, and congrats again on the great product.9 Replies
Hey sorry you are facing this issue. Looks like your workflowRun table does not have a state column. This column should have beeb added in 1.1.0 upgrade. Can you Check this column exist? (The migration command is just supposed to fill state column)
Hello @Rob could you please your workspace version from database ?
Default.core.workspace.version
I would recommend recovering a 1.1.0 backup and re attempt the upgrade and looking for migration errors in the twenty server logs
Thanks for the quick feedback!
I reverted (via database backup) to v1.0.3 and confirmed everything was working.
I then upgrade to v1.1.0. and then a range of migrations kick off (see attached migrations.txt). Which is then immediately followed by the attached errors.
It looks to me like the core issue is
QueryFailedError: relation "core.userWorkspaceRole" does not exist and I can not see this table in the database either. When should this have been created? can i kick off that process manually?
Thank you @martmull and @PrastoinAny advice on if this has been addressed in the latest 1.2 release? And if so, what the upgrade path should be given that 1.1 doesn’t work for me? @ɃØĦɆᵾS @Félix
I'm afraid I'm not sure how to help you with your problem, new release should be available on Monday once critical issues are solved
Unknown User•2mo ago
Message Not Public
Sign In & Join Server To View
Hi @Félix, thanks for your comment. Your info helped me find the issue and a past failed migration. I was manually able to run the required steps and now everything is working. Thank you!
Unknown User•2mo ago
Message Not Public
Sign In & Join Server To View
Hey @Rob, have you run the command atomically or through an upgrade one ?
I would recommend double checking your workspace version that should be equal to your currently installed twenty version