langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

After updating to 1.4, the conversation variable cannot be recognized when running after the release of the update. There is no such issue during preview during the development process #14080

New Issue
Closed
opened 2026-02-21 19:15:27 -05:00 by yindo · 9 comments
yindo commented 2026-02-21 19:15:27 -05:00
Owner
Copy Link
Copy Source

Originally created by @bixx2025 on GitHub (May 21, 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

1.4

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @bixx2025 on GitHub (May 21, 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 1.4 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/5c7a970f-24da-4826-8a9b-a145d02ae9be) ![Image](https://github.com/user-attachments/assets/e9055c27-5a17-456c-b230-216219143ebc) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 19:15:27 -05:00
yindo commented 2026-02-21 19:15:27 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 21, 2025):

Hello @bixx2025! I'm Dosu, your friendly bot here to help you with bugs, answer questions, and guide you in becoming a contributor. I'm ready to assist while we wait for a human maintainer. How can I help you today?

There is a known issue in Dify version 1.4 related to variable recognition, specifically when using multiple models and referencing variables in a model summary. This issue is caused by a bug in the Variable Aggregator introduced in version 1.4. To resolve this, you need to delete your existing container image and re-pull the v1.4.0 image. This should help address the problem you're experiencing with the conversation variable not being recognized after the update [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 (May 21, 2025): <!-- Greeting --> Hello @bixx2025! I'm [Dosu](https://dosu.dev), your friendly bot here to help you with bugs, answer questions, and guide you in becoming a contributor. I'm ready to assist while we wait for a human maintainer. How can I help you today? <!-- Answer --> There is a known issue in Dify version 1.4 related to variable recognition, specifically when using multiple models and referencing variables in a model summary. This issue is caused by a bug in the Variable Aggregator introduced in version 1.4. To resolve this, you need to delete your existing container image and re-pull the v1.4.0 image. This should help address the problem you're experiencing with the conversation variable not being recognized after the update <sup>[[1]](https://github.com/langgenius/dify/issues/19829)</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/1cc88f80-0b31-4681-b861-8371159132ca?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/1cc88f80-0b31-4681-b861-8371159132ca?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/1cc88f80-0b31-4681-b861-8371159132ca?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/1cc88f80-0b31-4681-b861-8371159132ca?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1cc88f80-0b31-4681-b861-8371159132ca?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/1cc88f80-0b31-4681-b861-8371159132ca?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1cc88f80-0b31-4681-b861-8371159132ca?feedback_type=other)</sup>
yindo commented 2026-02-21 19:15:27 -05:00
Author
Owner
Copy Link
Copy Source

@bixx2025 commented on GitHub (May 21, 2025):

@dosu Thanks a lot.Could you tell me how to re-pull the image?

@bixx2025 commented on GitHub (May 21, 2025): @dosu Thanks a lot.Could you tell me how to re-pull the image?
yindo commented 2026-02-21 19:15:28 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 21, 2025):

To re-pull the image, you can follow these steps:

  1. Stop the running container: Use the command docker stop <container_name> to stop the current container.

  2. Remove the existing container: Execute docker rm <container_name> to remove the stopped container.

  3. Remove the existing image: Run docker rmi <image_name>:v1.4.0 to delete the current image.

  4. Pull the latest image: Use docker pull <image_name>:v1.4.0 to download the latest version of the image.

  5. Run the container again: Start the container with the new image using docker run <options> <image_name>:v1.4.0.

Make sure to replace <container_name> and <image_name> with the actual names used in your setup. If you need further assistance, feel free to ask!

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 (May 21, 2025): <!-- Answer --> To re-pull the image, you can follow these steps: 1. **Stop the running container**: Use the command `docker stop <container_name>` to stop the current container. 2. **Remove the existing container**: Execute `docker rm <container_name>` to remove the stopped container. 3. **Remove the existing image**: Run `docker rmi <image_name>:v1.4.0` to delete the current image. 4. **Pull the latest image**: Use `docker pull <image_name>:v1.4.0` to download the latest version of the image. 5. **Run the container again**: Start the container with the new image using `docker run <options> <image_name>:v1.4.0`. Make sure to replace `<container_name>` and `<image_name>` with the actual names used in your setup. If you need further assistance, feel free to ask! <!-- 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/71ae84e8-49cb-44ef-b2a7-69d0115d7f38?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/71ae84e8-49cb-44ef-b2a7-69d0115d7f38?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/71ae84e8-49cb-44ef-b2a7-69d0115d7f38?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/71ae84e8-49cb-44ef-b2a7-69d0115d7f38?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/71ae84e8-49cb-44ef-b2a7-69d0115d7f38?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/71ae84e8-49cb-44ef-b2a7-69d0115d7f38?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/71ae84e8-49cb-44ef-b2a7-69d0115d7f38?feedback_type=other)</sup>
yindo commented 2026-02-21 19:15:28 -05:00
Author
Owner
Copy Link
Copy Source

@bixx2025 commented on GitHub (May 21, 2025):

@dosu Will this action delete the content in my existing dify? There are multiple images in the dify backend, do we need to delete each one? For example, Redis, nginx?

@bixx2025 commented on GitHub (May 21, 2025): @dosu Will this action delete the content in my existing dify? There are multiple images in the dify backend, do we need to delete each one? For example, Redis, nginx?
yindo commented 2026-02-21 19:15:28 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 21, 2025):

Re-pulling the Dify image will not delete the content in your existing setup, as long as you have properly configured Docker volumes for data persistence. These volumes ensure that your data is stored on the host machine and remains intact even if the containers are removed or updated [1].

You do not need to delete images for services like Redis and nginx unless you specifically want to update or change them. These services are independent and can be managed separately. If your issue is related only to the Dify application image, you can focus on updating that specific image without affecting other services [2].

Before performing any updates, it's recommended to back up your volume data to prevent any accidental data loss. Use sudo tar to create backups of your volumes, ensuring all files are preserved [3].

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 (May 21, 2025): <!-- Answer --> Re-pulling the Dify image will not delete the content in your existing setup, as long as you have properly configured Docker volumes for data persistence. These volumes ensure that your data is stored on the host machine and remains intact even if the containers are removed or updated <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/docker-compose-template.yaml)</sup>. You do not need to delete images for services like Redis and nginx unless you specifically want to update or change them. These services are independent and can be managed separately. If your issue is related only to the Dify application image, you can focus on updating that specific image without affecting other services <sup>[[2]](https://github.com/langgenius/dify/issues/14165)</sup>. Before performing any updates, it's recommended to back up your volume data to prevent any accidental data loss. Use `sudo tar` to create backups of your volumes, ensuring all files are preserved <sup>[[3]](https://github.com/langgenius/dify/issues/19806)</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/4346b454-1060-438f-b31d-3169a13907c2?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/4346b454-1060-438f-b31d-3169a13907c2?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/4346b454-1060-438f-b31d-3169a13907c2?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/4346b454-1060-438f-b31d-3169a13907c2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4346b454-1060-438f-b31d-3169a13907c2?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/4346b454-1060-438f-b31d-3169a13907c2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4346b454-1060-438f-b31d-3169a13907c2?feedback_type=other)</sup>
yindo commented 2026-02-21 19:15:28 -05:00
Author
Owner
Copy Link
Copy Source

@bixx2025 commented on GitHub (May 21, 2025):

@dosu Image , As shown in the Screenshot, could you tell me which container will to be deleted?

@bixx2025 commented on GitHub (May 21, 2025): @dosu ![Image](https://github.com/user-attachments/assets/309e8fbb-de65-4770-ad59-632237d3008f) , As shown in the Screenshot, could you tell me which container will to be deleted?
yindo commented 2026-02-21 19:15:28 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 21, 2025):

You should focus on deleting and re-pulling the container associated with the Dify application itself. Based on your screenshot, look for containers with names like "dify-api", "dify-web", or "dify-worker", as these are likely related to the core Dify application. You do not need to delete containers for services like Redis or the database unless you specifically want to update them. Concentrate on the containers directly related to the application experiencing the issue.

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 (May 21, 2025): <!-- Answer --> You should focus on deleting and re-pulling the container associated with the Dify application itself. Based on your screenshot, look for containers with names like "dify-api", "dify-web", or "dify-worker", as these are likely related to the core Dify application. You do not need to delete containers for services like Redis or the database unless you specifically want to update them. Concentrate on the containers directly related to the application experiencing the issue. <!-- 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/8df2fa6f-4159-44ad-9263-9184a8dbcf2a?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/8df2fa6f-4159-44ad-9263-9184a8dbcf2a?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/8df2fa6f-4159-44ad-9263-9184a8dbcf2a?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/8df2fa6f-4159-44ad-9263-9184a8dbcf2a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8df2fa6f-4159-44ad-9263-9184a8dbcf2a?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/8df2fa6f-4159-44ad-9263-9184a8dbcf2a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8df2fa6f-4159-44ad-9263-9184a8dbcf2a?feedback_type=other)</sup>
yindo commented 2026-02-21 19:15:28 -05:00
Author
Owner
Copy Link
Copy Source

@bixx2025 commented on GitHub (May 21, 2025):

@dosu Is there a sequence for starting these containers?

@bixx2025 commented on GitHub (May 21, 2025): @dosu Is there a sequence for starting these containers?
yindo commented 2026-02-21 19:15:28 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 21, 2025):

When starting the containers, it's generally a good practice to follow this sequence:

  1. Database: Start the database container first, as other services depend on it for data storage.
  2. Redis: Launch Redis next, as it may be used for caching and message brokering.
  3. Dify Core Services: Start the core Dify services like "dify-api", "dify-worker", and "dify-web". These services rely on the database and Redis to function correctly.
  4. Additional Services: Finally, start any additional services like "plugin daemon", "sandbox", or "SSRF proxy" as needed.

This sequence ensures that all dependencies are available when the application services start. If you have a docker-compose setup, it usually handles the order automatically based on service dependencies defined in the configuration.

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 (May 21, 2025): <!-- Answer --> When starting the containers, it's generally a good practice to follow this sequence: 1. **Database**: Start the database container first, as other services depend on it for data storage. 2. **Redis**: Launch Redis next, as it may be used for caching and message brokering. 3. **Dify Core Services**: Start the core Dify services like "dify-api", "dify-worker", and "dify-web". These services rely on the database and Redis to function correctly. 4. **Additional Services**: Finally, start any additional services like "plugin daemon", "sandbox", or "SSRF proxy" as needed. This sequence ensures that all dependencies are available when the application services start. If you have a `docker-compose` setup, it usually handles the order automatically based on service dependencies defined in the configuration. <!-- 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/1314efb0-fe76-4b7a-91bd-983fb0ef150b?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/1314efb0-fe76-4b7a-91bd-983fb0ef150b?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/1314efb0-fe76-4b7a-91bd-983fb0ef150b?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/1314efb0-fe76-4b7a-91bd-983fb0ef150b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1314efb0-fe76-4b7a-91bd-983fb0ef150b?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/1314efb0-fe76-4b7a-91bd-983fb0ef150b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1314efb0-fe76-4b7a-91bd-983fb0ef150b?feedback_type=other)</sup>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#14080
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?