How to upgrade dify across versions to complete missing tables. Upgrade from DIFY1.11.0 to version 1.14.0

[1107186916]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

How to upgrade dify across versions to complete missing tables. Upgrade from DIFY1.11.0 to version 1.14.0

[dosubot[bot]]

Dify uses Flask-Migrate (Alembic) for database schema management. When you upgrade, all intermediate migrations between your current version and the target version are executed sequentially. However, jumping directly from 1.11.0 to 1.14.0 can be risky — large version jumps have higher failure rates [1]. Here's the recommended approach:

Recommended: Incremental Upgrade Path

Upgrade through intermediate versions: 1.11.x → 1.12.x → 1.13.x → 1.14.x, verifying each step completes successfully before proceeding.

If you want to jump directly (Docker Compose):

# 1. Backup your database first
docker compose exec db_postgres pg_dump -U postgres dify > backup.sql

# 2. Stop containers
docker compose down

# 3. Pull the target version
git pull origin main
docker compose pull

# 4. Sync environment variables (important for multi-version jumps)
bash dify-env-sync.sh

# 5. Start containers — migrations run automatically if MIGRATION_ENABLED=true
docker compose up -d

Migrations execute automatically on startup [2]. If they fail, run manually:

docker compose exec api flask db upgrade

If you encounter missing tables after the upgrade:

# Check migration status
docker compose exec api flask db history

# If alembic_version is out of sync, reset it
docker compose exec db_postgres psql -U postgres -d dify -c \
  "DROP TABLE IF EXISTS alembic_version CASCADE;"

# Re-run all migrations from scratch
docker compose exec api flask db upgrade

This forces Alembic to re-evaluate and apply all migrations that haven't been executed [3].

Additional steps for plugin migrations (required for 1.11→1.14):

docker compose exec api uv run flask extract-plugins --workers=20
docker compose exec api uv run flask install-plugins --workers=2
docker compose exec api uv run flask migrate-data-for-plugin

Key tips:

• Ensure MIGRATION_ENABLED=true in your .env [4]
• From v1.10.1+, containers run as UID 1001 — fix storage permissions if needed: sudo chown -R 1001:1001 ./volumes/app/storage [1]
• Check that COMPOSE_PROFILES includes your database type (e.g., weaviate,postgresql) as this became mandatory around 1.12.x [1]

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.