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

XML issues shown in the log #20815

New Issue
Closed
opened 2026-02-21 20:09:06 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:09:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @1063895007 on GitHub (Dec 4, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.9.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

The XML displayed in the log only shows a part of it and is not complete, while the "Conversation Log" "Trace" contains the complete XML content.

✔️ Expected Behavior

I hope the complete XML content can be displayed in the conversation log.

❌ Actual Behavior

No response

Originally created by @1063895007 on GitHub (Dec 4, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.9.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="1117" height="814" alt="Image" src="https://github.com/user-attachments/assets/fbad87be-3146-426e-a119-485bc539c80e" /> The XML displayed in the log only shows a part of it and is not complete, while the "Conversation Log" "Trace" contains the complete XML content. ### ✔️ Expected Behavior I hope the complete XML content can be displayed in the conversation log. ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 20:09:06 -05:00
yindo closed this issue 2026-02-21 20:09:06 -05:00
yindo commented 2026-02-21 20:09:06 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 4, 2025):

Hi @1063895007! I'm Dosu and I’m helping the dify team.

The reason only partial XML is shown in the conversation log is that Dify uses different data pipelines for the conversation log and the Conversation Log/Trace. The conversation log displays summary fields from chat/conversation APIs, which often truncate or simplify message content (like XML). In contrast, the Conversation Log/Trace accesses workflow run endpoints that provide the full output, including complete XML. The UI for the trace view also offers a download link for the full content if truncation occurs, while the main log view does not fetch or render the full XML by design1 2 .

There are no recent pull requests or issues addressing this limitation. However, some users have suggested setting the environment variable DEBUG=true in your Docker deployment, which may enable more detailed logs and potentially more complete XML content in some views3 .

If you need the complete XML, you can access it via the Conversation Log/Trace modal or download it from the trace view when available. To change this behavior in the main conversation log, a code change would be required to fetch and display the full workflow output instead of the summary.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Dec 4, 2025): <!-- Greeting --> Hi @1063895007! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The reason only partial XML is shown in the conversation log is that Dify uses different data pipelines for the conversation log and the Conversation Log/Trace. The conversation log displays summary fields from chat/conversation APIs, which often truncate or simplify message content (like XML). In contrast, the Conversation Log/Trace accesses workflow run endpoints that provide the full output, including complete XML. The UI for the trace view also offers a download link for the full content if truncation occurs, while the main log view does not fetch or render the full XML by design[^1][^2]. There are no recent pull requests or issues addressing this limitation. However, some users have suggested setting the environment variable `DEBUG=true` in your Docker deployment, which may enable more detailed logs and potentially more complete XML content in some views[^3]. [^1]: [Backend API field definitions and truncation logic](https://github.com/langgenius/dify/blob/b927ff9fcf895184f504129046206879a70242d4/api/fields/conversation_fields.py#L9-L152) [^2]: [Frontend workflow run detail and trace rendering](https://github.com/langgenius/dify/blob/b927ff9fcf895184f504129046206879a70242d4/web/app/components/workflow/run/index.tsx#L19-L197) [^3]: [Community suggestion to set DEBUG=true](https://github.com/langgenius/dify/discussions/26471) If you need the complete XML, you can access it via the Conversation Log/Trace modal or download it from the trace view when available. To change this behavior in the main conversation log, a code change would be required to fetch and display the full workflow output instead of the summary. <!-- 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/a66f43e6-3fae-45a9-a103-34d332b33a98?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a66f43e6-3fae-45a9-a103-34d332b33a98?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a66f43e6-3fae-45a9-a103-34d332b33a98?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a66f43e6-3fae-45a9-a103-34d332b33a98?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a66f43e6-3fae-45a9-a103-34d332b33a98?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a66f43e6-3fae-45a9-a103-34d332b33a98?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a66f43e6-3fae-45a9-a103-34d332b33a98?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20reason%20only%20partial%20XML%20is%20shown%20in%20the%20conversation%20log%20is%20that%20Dify%20uses%20different%20data%20pipelines%20for%20the%20conversation%20log%20and%20the%20Conversation%20Log/Trace.%20The%20conversation%20log%20displays%20summary%20fields%20from%20chat/conversation%20APIs%2C%20which%20often%20truncate%20or%20simplify%20message%20content%20%28like%20XML%29.%20In%20contrast%2C%20the%20Conversation%20Log/Trace%20accesses%20workflow%20run%20endpoints%20that%20provide%20the%20full%20output%2C%20including%20complete%20XML.%20The%20UI%20for%20the%20trace%20view%20also%20offers%20a%20download%20link%20for%20the%20full%20content%20if%20truncation%20occurs%2C%20while%20the%20main%20log%20view%20does%20not%20fetch%20or%20render%20the%20full%20XML%20by%20design%5B%5E1%5D%5B%5E2%5D.%0A%0AThere%20are%20no%20recent%20pull%20requests%20or%20issues%20addressing%20this%20limitation.%20However%2C%20some%20users%20have%20suggested%20setting%20the%20environment%20variable%20%60DEBUG%3Dtrue%60%20in%20your%20Docker%20deployment%2C%20which%20may%20enable%20more%20detailed%20logs%20and%20potentially%20more%20complete%20XML%20content%20in%20some%20views%5B%5E3%5D.%0A%0A%5B%5E1%5D%3A%20%5BBackend%20API%20field%20definitions%20and%20truncation%20logic%5D%28https%3A//github.com/langgenius/dify/blob/b927ff9fcf895184f504129046206879a70242d4/api/fields/conversation_fields.py%23L9-L152%29%0A%5B%5E2%5D%3A%20%5BFrontend%20workflow%20run%20detail%20and%20trace%20rendering%5D%28https%3A//github.com/langgenius/dify/blob/b927ff9fcf895184f504129046206879a70242d4/web/app/components/workflow/run/index.tsx%23L19-L197%29%0A%5B%5E3%5D%3A%20%5BCommunity%20suggestion%20to%20set%20DEBUG%3Dtrue%5D%28https%3A//github.com/langgenius/dify/discussions/26471%29%0A%0AIf%20you%20need%20the%20complete%20XML%2C%20you%20can%20access%20it%20via%20the%20Conversation%20Log/Trace%20modal%20or%20download%20it%20from%20the%20trace%20view%20when%20available.%20To%20change%20this%20behavior%20in%20the%20main%20conversation%20log%2C%20a%20code%20change%20would%20be%20required%20to%20fetch%20and%20display%20the%20full%20workflow%20output%20instead%20of%20the%20summary.)&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/29171)
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#20815
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?