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

Tracking Chatflow log Application error #20321

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

Originally created by @lework on GitHub (Nov 13, 2025).

Originally assigned to: @hjlarry on GitHub.

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image Image Image

✔️ Expected Behavior

Normal tracking

❌ Actual Behavior

Application error

Originally created by @lework on GitHub (Nov 13, 2025). Originally assigned to: @hjlarry on GitHub. ### 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.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="1075" height="333" alt="Image" src="https://github.com/user-attachments/assets/763fba71-53e7-48a8-b8f6-ea6f80ea5fde" /> <img width="602" height="175" alt="Image" src="https://github.com/user-attachments/assets/dd08bb91-2552-4d2c-994c-a1b5f866f737" /> <img width="1486" height="804" alt="Image" src="https://github.com/user-attachments/assets/aebdf6ff-edf9-4b50-9009-a1f661c5b836" /> ### ✔️ Expected Behavior Normal tracking ### ❌ Actual Behavior Application error
yindo added the 🐞 bug label 2026-02-21 20:06:48 -05:00
yindo closed this issue 2026-02-21 20:06:49 -05:00
yindo commented 2026-02-21 20:06:49 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 13, 2025):

The error occurs because a component that consumes WorkflowContext is rendered outside of its provider, often in a modal or dialog related to Chatflow log tracking. In Dify's frontend, WorkflowContext.Provider is defined in web/app/components/workflow/context/WorkflowContext.ts and provided in web/app/components/workflow/Workflow.tsx. If a consumer (like a log details modal) is rendered outside this provider, you'll see the "Missing WorkflowContext.Provider in the tree" error reference.

To fix this, ensure any component that uses WorkflowContext is always wrapped in a WorkflowContext.Provider. For example, if you render a modal or panel that needs workflow context, refactor its invocation so it is a child of the provider, or wrap it with the provider when rendering. This may require moving modal/dialog rendering up into the workflow tree or explicitly wrapping them.

No existing issues or merged pull requests directly address this error, so a code-level refactor is likely needed reference.

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Nov 13, 2025): <!-- Answer --> The error occurs because a component that consumes `WorkflowContext` is rendered outside of its provider, often in a modal or dialog related to Chatflow log tracking. In Dify's frontend, `WorkflowContext.Provider` is defined in `web/app/components/workflow/context/WorkflowContext.ts` and provided in `web/app/components/workflow/Workflow.tsx`. If a consumer (like a log details modal) is rendered outside this provider, you'll see the "Missing WorkflowContext.Provider in the tree" error [reference](https://github.com/langgenius/dify/blob/1e6d0de48bbc08b069f721fd615b18ed277b695b/web/app/components/base/message-log-modal/index.tsx#L18-L74). To fix this, ensure any component that uses `WorkflowContext` is always wrapped in a `WorkflowContext.Provider`. For example, if you render a modal or panel that needs workflow context, refactor its invocation so it is a child of the provider, or wrap it with the provider when rendering. This may require moving modal/dialog rendering up into the workflow tree or explicitly wrapping them. No existing issues or merged pull requests directly address this error, so a code-level refactor is likely needed [reference](https://github.com/langgenius/dify/blob/1e6d0de48bbc08b069f721fd615b18ed277b695b/web/app/components/workflow/panel/chat-record/index.tsx#L14-L140). <!-- 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/61d31ced-ce56-42d5-8bd1-5f666e2f03c3?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/61d31ced-ce56-42d5-8bd1-5f666e2f03c3?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/61d31ced-ce56-42d5-8bd1-5f666e2f03c3?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/61d31ced-ce56-42d5-8bd1-5f666e2f03c3?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/61d31ced-ce56-42d5-8bd1-5f666e2f03c3?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/61d31ced-ce56-42d5-8bd1-5f666e2f03c3?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/61d31ced-ce56-42d5-8bd1-5f666e2f03c3?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&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/28211)
yindo commented 2026-02-21 20:06:49 -05:00
Author
Owner
Copy Link
Copy Source

@Lygggggg commented on GitHub (Nov 14, 2025):

how to repair it？

@Lygggggg commented on GitHub (Nov 14, 2025): how to repair it？
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#20321
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?