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

Variable #1749624841670.text# not found #14751

New Issue
Closed
opened 2026-02-21 19:18:37 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:18:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @LMJOK on GitHub (Jun 19, 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

LLM

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @LMJOK on GitHub (Jun 19, 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 LLM ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/0c967b29-c328-44e0-b4ef-958775aa8559) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🤔 cant-reproduce label 2026-02-21 19:18:37 -05:00
yindo closed this issue 2026-02-21 19:18:37 -05:00
yindo commented 2026-02-21 19:18:37 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 19, 2025):

The error Variable #1749624841670.text# not found means that a variable referenced in your workflow or prompt template could not be resolved at runtime. This typically happens if the variable is missing, not produced by an upstream node, or there is a naming mismatch in your workflow configuration. The error is raised by the variable resolution logic in Dify's backend when it cannot find the expected variable in the variable pool during execution (source).

Common causes include:

  • The node or step that should produce this variable did not run or failed.
  • The variable name in your template does not match the output variable name of the upstream node.
  • There is a broken selector path or a typo in the variable reference.

Recent changes in Dify have added stricter checks for variable keys and improved error reporting, so this error may surface if your workflow references a variable that is not properly defined or connected (source).

To resolve:

  • Double-check your workflow graph to ensure all variable references (like #1749624841670.text#) are produced by an upstream node and the names match exactly.
  • Make sure you have published your workflow after making changes, as unpublished changes won't take effect (source).
  • If you recently upgraded or changed variable types, review any new validation or requirements for variable keys.

If you need more targeted help, sharing the relevant part of your workflow configuration or template where this variable is referenced can help pinpoint the issue.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jun 19, 2025): <!-- Answer --> The error `Variable #1749624841670.text# not found` means that a variable referenced in your workflow or prompt template could not be resolved at runtime. This typically happens if the variable is missing, not produced by an upstream node, or there is a naming mismatch in your workflow configuration. The error is raised by the variable resolution logic in Dify's backend when it cannot find the expected variable in the variable pool during execution ([source](https://github.com/langgenius/dify/blob/d34795fc08383d5de45b7388b89bd4a5af8ad025/api/core/workflow/nodes/llm/node.py)). Common causes include: - The node or step that should produce this variable did not run or failed. - The variable name in your template does not match the output variable name of the upstream node. - There is a broken selector path or a typo in the variable reference. Recent changes in Dify have added stricter checks for variable keys and improved error reporting, so this error may surface if your workflow references a variable that is not properly defined or connected ([source](https://github.com/langgenius/dify/pull/21057)). To resolve: - Double-check your workflow graph to ensure all variable references (like `#1749624841670.text#`) are produced by an upstream node and the names match exactly. - Make sure you have published your workflow after making changes, as unpublished changes won't take effect ([source](https://github.com/langgenius/dify/issues/19329)). - If you recently upgraded or changed variable types, review any new validation or requirements for variable keys. If you need more targeted help, sharing the relevant part of your workflow configuration or template where this variable is referenced can help pinpoint the issue. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/20773501-ebb0-4e07-b5a9-683c53476c34?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/20773501-ebb0-4e07-b5a9-683c53476c34?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/20773501-ebb0-4e07-b5a9-683c53476c34?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/20773501-ebb0-4e07-b5a9-683c53476c34?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/20773501-ebb0-4e07-b5a9-683c53476c34?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/20773501-ebb0-4e07-b5a9-683c53476c34?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/20773501-ebb0-4e07-b5a9-683c53476c34?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/21268)
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 🤔 cant-reproduce
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#14751
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?