[Migration Issue] When upgrade from v3.3.0 to v3.4.2
hi team, somehow we have this error when try to upgrade the version. may we know what is the best practice approach for this issue?
AHi @Anggakara, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
AAnswer
I wasn't able to find a direct answer, here are some relevant sources:
- [Technical Advisory 10005][(4) ]: Describes expected downtime during upgrades and migration issues when upgrading from version 2.39.0, specifically mentioning storage optimizations that replace database tables during setup.
- [migration error updating from 2.20.2 to 2.22.3][(8) ]: Shows a community discussion about migration failures where the solution was to run
zitadel setup cleanupcommand to resolve stuck migrations.
AAFeel free to tag @Ask Inkeep with additional questions.
AGot it. Tagging @Rajat for additional help.
Rhey @Anggakara welcome to the server and thaks for your question, this seems to be a warning alert built for your convenience. Did you face any errors as such while mugrating?. did it got stuck somewhere?. If it will be an error, then it will be
level=error instead of level=warning msg
Ai see thank you for the answer @Rajat , somehow it stuck when there's a failure on the migration. when we clear the migration version in the db and run it again it working fine. i think it's expected
G
Looks like you just helped out another community member! Thanks for being so helpful @289977372185329665! You're now one step closer to leveling up—keep up the amazing peer support! 
AGlad I could be helpful. Feel free to create a new thread with any new questions you may have.