api-1 report error:ERROR [flask_migrate] Error: Can't locate revision identified by 'd20049ed0af6' #12310

Closed
opened 2026-02-21 19:06:50 -05:00 by yindo · 2 comments
Owner

Originally created by @qzq-web on GitHub (Mar 28, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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.

Dify version

0.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

non

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @qzq-web on GitHub (Mar 28, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce non ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:06:50 -05:00
yindo closed this issue 2026-02-21 19:06:50 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Mar 28, 2025):

Hello, @qzq-web! I'm here to help you with any bugs, questions, or contributions you have for the Dify project. Let me know how I can assist you!

To resolve the error "Can't locate revision identified by 'd20049ed0af6'" in your Dify version 0.15.3 setup using Docker, you can follow these steps:

  1. Drop the alembic_version table completely:

    DROP TABLE alembic_version;
    

    Then reinitialize the migrations.

  2. Update the version_num in the alembic_version table to match the correct revision for version 0.15.3.

After applying either solution, the services should start normally with version 0.15.3 [1].

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 28, 2025): <!-- Greeting --> Hello, @qzq-web! I'm here to help you with any bugs, questions, or contributions you have for the Dify project. Let me know how I can assist you! <!-- Answer --> To resolve the error "Can't locate revision identified by 'd20049ed0af6'" in your Dify version 0.15.3 setup using Docker, you can follow these steps: 1. **Drop the alembic_version table completely:** ```sql DROP TABLE alembic_version; ``` Then reinitialize the migrations. 2. **Update the version_num in the alembic_version table to match the correct revision for version 0.15.3.** After applying either solution, the services should start normally with version 0.15.3 <sup>[[1]](https://github.com/langgenius/dify/issues/15220)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/185159eb-aa99-476e-a684-7ab4547871a0?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/185159eb-aa99-476e-a684-7ab4547871a0?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/185159eb-aa99-476e-a684-7ab4547871a0?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/185159eb-aa99-476e-a684-7ab4547871a0?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/185159eb-aa99-476e-a684-7ab4547871a0?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/185159eb-aa99-476e-a684-7ab4547871a0?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/185159eb-aa99-476e-a684-7ab4547871a0?feedback_type=other)</sup>
Author
Owner

@qzq-web commented on GitHub (Mar 28, 2025):

Stop and clean up existing containers and volumes:
docker-compose down -v
Disable Docker build cache to rebuild the image:
docker-compose build --no-cache
Then start again and the problem is solved:
docker compose up -d

@qzq-web commented on GitHub (Mar 28, 2025): Stop and clean up existing containers and volumes: `docker-compose down -v` Disable Docker build cache to rebuild the image: `docker-compose build --no-cache` Then start again and the problem is solved: `docker compose up -d`
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#12310