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

Did not display file url in run mode despite still having url in the tracing #6196

New Issue
Closed
opened 2026-02-21 18:14:30 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 18:14:30 -05:00
Owner
Copy Link
Copy Source

Originally created by @1linedata on GitHub (Oct 21, 2024).

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.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Screenshot 2024-10-22 053326 Screenshot 2024-10-22 053342 Screenshot 2024-10-22 053316

Did not display file url in run mode despite still having url in the tracing

✔️ Expected Behavior

display file url in run mode (same with url in the tracing)

❌ Actual Behavior

Did not display file url in run mode despite still having url in the tracing

Originally created by @1linedata on GitHub (Oct 21, 2024). ### 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.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="573" alt="Screenshot 2024-10-22 053326" src="https://github.com/user-attachments/assets/f51f05ad-a574-406c-ad7b-880ca1f8c835"> <img width="569" alt="Screenshot 2024-10-22 053342" src="https://github.com/user-attachments/assets/636eef35-a9f3-4c77-96e1-5e468b7a1495"> <img width="563" alt="Screenshot 2024-10-22 053316" src="https://github.com/user-attachments/assets/97f81a4b-a39a-4812-bfaa-8f05fde6b302"> Did not display file url in run mode despite still having url in the tracing ### ✔️ Expected Behavior display file url in run mode (same with url in the tracing) ### ❌ Actual Behavior Did not display file url in run mode despite still having url in the tracing
yindo added the 🐞 bug label 2026-02-21 18:14:30 -05:00
yindo closed this issue 2026-02-21 18:14:30 -05:00
yindo commented 2026-02-21 18:14:30 -05:00
Author
Owner
Copy Link
Copy Source

@1linedata commented on GitHub (Oct 21, 2024):

sorry for mistaken 1 info above, I'm currently using cloud version not self hosted (docker)

@1linedata commented on GitHub (Oct 21, 2024): sorry for mistaken 1 info above, I'm currently using cloud version not self hosted (docker)
yindo commented 2026-02-21 18:14:30 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 21, 2024):

Hello, @1linedata! I'm here to help you with bug fixes, answer questions, and even guide you on how to contribute. Let's tackle this issue together!

The issue you're experiencing, where the file URL is not displayed in run mode but is present in tracing mode, might be related to how Dify handles file inputs and outputs in workflows. The logic for this is implemented in the ToolNode class within the api/core/workflow/nodes/tool/tool_node.py file. This class includes methods for processing tool messages and handling file storage and extraction, such as _convert_tool_messages, _extract_tool_response_binary, _extract_tool_response_text, and _extract_tool_response_json [1].

If the file URL is not appearing in run mode, it could be due to differences in how these modes handle or display file-related data. Unfortunately, specific details about discrepancies between run mode and tracing mode outputs, or configuration settings affecting file URL visibility, are not available in the provided information. You might want to check the implementation in the mentioned file for any conditions or configurations that could affect this behavior.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Oct 21, 2024): <!-- Greeting --> Hello, @1linedata! I'm here to help you with bug fixes, answer questions, and even guide you on how to contribute. Let's tackle this issue together! <!-- Answer --> The issue you're experiencing, where the file URL is not displayed in run mode but is present in tracing mode, might be related to how Dify handles file inputs and outputs in workflows. The logic for this is implemented in the `ToolNode` class within the `api/core/workflow/nodes/tool/tool_node.py` file. This class includes methods for processing tool messages and handling file storage and extraction, such as `_convert_tool_messages`, `_extract_tool_response_binary`, `_extract_tool_response_text`, and `_extract_tool_response_json` <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/workflow/nodes/tool/tool_node.py)</sup>. If the file URL is not appearing in run mode, it could be due to differences in how these modes handle or display file-related data. Unfortunately, specific details about discrepancies between run mode and tracing mode outputs, or configuration settings affecting file URL visibility, are not available in the provided information. You might want to check the implementation in the mentioned file for any conditions or configurations that could affect this behavior. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:14:30 -05:00
Author
Owner
Copy Link
Copy Source

@hjlarry commented on GitHub (Oct 21, 2024):

duplicated with https://github.com/langgenius/dify/issues/9567

@hjlarry commented on GitHub (Oct 21, 2024): duplicated with https://github.com/langgenius/dify/issues/9567
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#6196
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?