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

Can not insert knowledgebase context variable mark into a prompt of a LLM node #14970

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

Originally created by @henrybjsoft on GitHub (Jun 27, 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.5

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I upgraded Dify from version 1.4.3 to the latest 1.5 version today.
I encountered a potential bug in a workflow application:
Issue Description
I can no longer insert a knowledge base context variable into the prompt box of an LLM node.

Steps to Reproduce

In a workflow application, create a sequence:
Knowledge Retrieval Node → LLM Node
Configure the LLM node:
Select "Knowledge Retrieval Result" as context
In the prompt editor, type / to open the variable menu
Select "Context" option
​Expected Behavior:
Insert context variable tag (e.g., {{knowledge_retrieval_result}})
​Actual Behavior:
No response after selection
Variable insertion fails silently
Current Impact
The workflow editor becomes uneditable for this configuration, preventing application modification.

Additional Context

Previous working version: 1.4.3
Upgraded version: 1.5.0

This regression breaks existing workflow configurations relying on context variable injection. Could you please investigate this issue?

✔️ Expected Behavior

Insert context variable tag (e.g., {{knowledge_retrieval_result}})

❌ Actual Behavior

No response after selection
Variable insertion fails silently

Originally created by @henrybjsoft on GitHub (Jun 27, 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.5 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I upgraded Dify from version 1.4.3 to the latest 1.5 version today. I encountered a potential bug in a workflow application: Issue Description I can no longer insert a knowledge base context variable into the prompt box of an LLM node. Steps to Reproduce In a workflow application, create a sequence: Knowledge Retrieval Node → LLM Node Configure the LLM node: Select "Knowledge Retrieval Result" as context In the prompt editor, type / to open the variable menu Select "Context" option ​Expected Behavior: Insert context variable tag (e.g., {{knowledge_retrieval_result}}) ​Actual Behavior: No response after selection Variable insertion fails silently Current Impact The workflow editor becomes uneditable for this configuration, preventing application modification. Additional Context Previous working version: 1.4.3 Upgraded version: 1.5.0 This regression breaks existing workflow configurations relying on context variable injection. Could you please investigate this issue? ### ✔️ Expected Behavior Insert context variable tag (e.g., {{knowledge_retrieval_result}}) ### ❌ Actual Behavior No response after selection Variable insertion fails silently
yindo added the 🐞 bug label 2026-02-21 19:19:35 -05:00
yindo closed this issue 2026-02-21 19:19:35 -05:00
yindo commented 2026-02-21 19:19:36 -05:00
Author
Owner
Copy Link
Copy Source

@henrybjsoft commented on GitHub (Jun 27, 2025):

Update: I modified the docker-compose.yaml file to configure the web application to use the 1.4.3 image. After restarting, the context variable tag started working again.

@henrybjsoft commented on GitHub (Jun 27, 2025): Update: I modified the docker-compose.yaml file to configure the web application to use the 1.4.3 image. After restarting, the context variable tag started working again.
yindo commented 2026-02-21 19:19:36 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jun 27, 2025):

Duplicated https://github.com/langgenius/dify/issues/21552
Already fixed in https://github.com/langgenius/dify/pull/21526

Please search the existing issue before posting one.

@crazywoola commented on GitHub (Jun 27, 2025): Duplicated https://github.com/langgenius/dify/issues/21552 Already fixed in https://github.com/langgenius/dify/pull/21526 Please search the existing issue before posting one.
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 🐞 bug
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#14970
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?