Anggakara
Anggakara16h ago

[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?
2025-10-21T02:33:04.328583424Z time="2025-10-21T02:33:04Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:130" migration step=repeatable_migrate_river
2025-10-21T02:33:04.328583424Z time="2025-10-21T02:33:04Z" level=warning msg="migration already started, will check again in 5 seconds" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:130" migration step=repeatable_migrate_river
1 Reply
Ask Inkeep
Ask Inkeep16h ago
Hi @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. Answer I wasn't able to find a direct answer, here are some relevant sources: 1. [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. 2. [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 cleanup command to resolve stuck migrations. Feel free to tag @Ask Inkeep with additional questions. Got it. Tagging @Rajat for additional help.

Did you find this page helpful?