Missing WorkflowContext.Provider in the tree #20411

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

v1.10

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

✔️ Expected Behavior

应该显示

❌ Actual Behavior

No response

Originally created by @DepengZou on GitHub (Nov 19, 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 v1.10 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="1645" height="493" alt="Image" src="https://github.com/user-attachments/assets/09bfa86f-2d42-4ca5-834c-fbe44cceaafe" /> ### ✔️ Expected Behavior 应该显示 <img width="603" height="250" alt="Image" src="https://github.com/user-attachments/assets/540c931b-33dd-4bb3-adeb-85874eb8b6ce" /> ### ❌ Actual Behavior _No response_

yindo added the 🐞 bug label 2026-02-21 20:07:19 -05:00

yindo closed this issue

yindo commented

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

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

The error "Missing WorkflowContext.Provider in the tree" happens when a component that uses the workflow context (like the workflow steps UI or log modals) is rendered outside of the required provider. In Dify, the WorkflowContextProvider is responsible for supplying this context, and any component using workflow state (via hooks like useStore or useWorkflowStore) must be a descendant of this provider in the React tree. If not, you'll see missing UI or errors, as you described.

This issue often appears in log panels or modals that display workflow run details. The fix is to ensure that any such component is wrapped in a WorkflowContextProvider. For example, the DetailPanel and MessageLogModal components are explicitly wrapped with WorkflowContextProvider in the codebase to avoid this error. If you have customizations or are using a version before a recent fix, check that your modal or detail components are wrapped correctly. See the relevant code and merged fix here: fix: click log panel of log page cause whole page crash.

If you are running Dify via Docker, make sure you have pulled the latest images and restarted your containers, as simply restarting without pulling may not update the frontend code that contains the fix. If you are still seeing the issue after updating, check your browser console for stack traces to identify which component is missing the provider and adjust your component tree accordingly.

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Nov 19, 2025):  Hi @DepengZou! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team.  The error "Missing WorkflowContext.Provider in the tree" happens when a component that uses the workflow context (like the workflow steps UI or log modals) is rendered outside of the required provider. In Dify, the WorkflowContextProvider is responsible for supplying this context, and any component using workflow state (via hooks like useStore or useWorkflowStore) must be a descendant of this provider in the React tree. If not, you'll see missing UI or errors, as you described. This issue often appears in log panels or modals that display workflow run details. The fix is to ensure that any such component is wrapped in a WorkflowContextProvider. For example, the DetailPanel and MessageLogModal components are explicitly wrapped with WorkflowContextProvider in the codebase to avoid this error. If you have customizations or are using a version before a recent fix, check that your modal or detail components are wrapped correctly. See the relevant code and merged fix here: [fix: click log panel of log page cause whole page crash](https://github.com/langgenius/dify/pull/28218). If you are running Dify via Docker, make sure you have pulled the latest images and restarted your containers, as simply restarting without pulling may not update the frontend code that contains the fix. If you are still seeing the issue after updating, check your browser console for stack traces to identify which component is missing the provider and adjust your component tree accordingly.  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/e8ec485b-2cc0-42c6-814e-b31de412abbc?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e8ec485b-2cc0-42c6-814e-b31de412abbc?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e8ec485b-2cc0-42c6-814e-b31de412abbc?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e8ec485b-2cc0-42c6-814e-b31de412abbc?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e8ec485b-2cc0-42c6-814e-b31de412abbc?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e8ec485b-2cc0-42c6-814e-b31de412abbc?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e8ec485b-2cc0-42c6-814e-b31de412abbc?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) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![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/28400)

yindo commented

@GRCmade commented on GitHub (Nov 19, 2025):

chatflow have the same problem

@GRCmade commented on GitHub (Nov 19, 2025): chatflow have the same problem

yindo commented

@xuliang5114923 commented on GitHub (Nov 20, 2025):

I have the same problem.

@xuliang5114923 commented on GitHub (Nov 20, 2025): I have the same problem.

yindo commented

@jlfloresTeika commented on GitHub (Nov 21, 2025):

Same problem here

@jlfloresTeika commented on GitHub (Nov 21, 2025): Same problem here

yindo commented

@jp-sft commented on GitHub (Nov 24, 2025):

sameproblem.com

@jp-sft commented on GitHub (Nov 24, 2025): sameproblem.com

yindo commented

@812432499c-svg commented on GitHub (Nov 24, 2025):

I have the same problem.

@812432499c-svg commented on GitHub (Nov 24, 2025): I have the same problem.

yindo commented

@wzn1KhUGCtAj commented on GitHub (Nov 24, 2025):

I have the same issue, and I'm sure I pulled the latest Docker image of version 1.10. Both the web and API version numbers are 1.10. I also tried opening it with multiple browsers, but the result remains the same.

@wzn1KhUGCtAj commented on GitHub (Nov 24, 2025): I have the same issue, and I'm sure I pulled the latest Docker image of version 1.10. Both the web and API version numbers are 1.10. I also tried opening it with multiple browsers, but the result remains the same. <img width="1603" height="1423" alt="Image" src="https://github.com/user-attachments/assets/d44a9143-875b-48ae-81d4-ad5429aaf75f" />

yindo commented

@wzn1KhUGCtAj commented on GitHub (Nov 24, 2025):

@wzn1KhUGCtAj commented on GitHub (Nov 24, 2025): <img width="1479" height="394" alt="Image" src="https://github.com/user-attachments/assets/e525a356-26c1-4f05-a5d4-882ae150c3d8" />

yindo commented

@wzn1KhUGCtAj commented on GitHub (Nov 24, 2025):

18671-56c632b04446c904.js:1 Uncaught Error: Missing WorkflowContext.Provider in the tree
at c (18671-56c632b04446c904.js:1:85707)
at c (82917-83d1cb2dae293dfc.js:1:2537)
at l9 (2de95d4b-8278ff6b72f9ce97.js:1:51131)
at o_ (2de95d4b-8278ff6b72f9ce97.js:1:70991)
at oq (2de95d4b-8278ff6b72f9ce97.js:1:82021)
at ik (2de95d4b-8278ff6b72f9ce97.js:1:114683)
at 2de95d4b-8278ff6b72f9ce97.js:1:114528
at ib (2de95d4b-8278ff6b72f9ce97.js:1:114536)
at iu (2de95d4b-8278ff6b72f9ce97.js:1:111619)
at iX (2de95d4b-8278ff6b72f9ce97.js:1:132935)
at MessagePort.w (3427-925d409d2d703f7f.js:1:148341)
c @ 18671-56c632b04446c904.js:1
c @ 82917-83d1cb2dae293dfc.js:1
l9 @ 2de95d4b-8278ff6b72f9ce97.js:1
o_ @ 2de95d4b-8278ff6b72f9ce97.js:1
oq @ 2de95d4b-8278ff6b72f9ce97.js:1
ik @ 2de95d4b-8278ff6b72f9ce97.js:1
(匿名) @ 2de95d4b-8278ff6b72f9ce97.js:1
ib @ 2de95d4b-8278ff6b72f9ce97.js:1
iu @ 2de95d4b-8278ff6b72f9ce97.js:1
iX @ 2de95d4b-8278ff6b72f9ce97.js:1
w @ 3427-925d409d2d703f7f.js:1

@wzn1KhUGCtAj commented on GitHub (Nov 24, 2025): 18671-56c632b04446c904.js:1 Uncaught Error: Missing WorkflowContext.Provider in the tree at c (18671-56c632b04446c904.js:1:85707) at c (82917-83d1cb2dae293dfc.js:1:2537) at l9 (2de95d4b-8278ff6b72f9ce97.js:1:51131) at o_ (2de95d4b-8278ff6b72f9ce97.js:1:70991) at oq (2de95d4b-8278ff6b72f9ce97.js:1:82021) at ik (2de95d4b-8278ff6b72f9ce97.js:1:114683) at 2de95d4b-8278ff6b72f9ce97.js:1:114528 at ib (2de95d4b-8278ff6b72f9ce97.js:1:114536) at iu (2de95d4b-8278ff6b72f9ce97.js:1:111619) at iX (2de95d4b-8278ff6b72f9ce97.js:1:132935) at MessagePort.w (3427-925d409d2d703f7f.js:1:148341) c @ 18671-56c632b04446c904.js:1 c @ 82917-83d1cb2dae293dfc.js:1 l9 @ 2de95d4b-8278ff6b72f9ce97.js:1 o_ @ 2de95d4b-8278ff6b72f9ce97.js:1 oq @ 2de95d4b-8278ff6b72f9ce97.js:1 ik @ 2de95d4b-8278ff6b72f9ce97.js:1 (匿名) @ 2de95d4b-8278ff6b72f9ce97.js:1 ib @ 2de95d4b-8278ff6b72f9ce97.js:1 iu @ 2de95d4b-8278ff6b72f9ce97.js:1 iX @ 2de95d4b-8278ff6b72f9ce97.js:1 w @ 3427-925d409d2d703f7f.js:1

yindo commented

@koking0 commented on GitHub (Nov 25, 2025):

same problem

@koking0 commented on GitHub (Nov 25, 2025): same problem

yindo commented

@rstraszewski commented on GitHub (Nov 25, 2025):

same problem

@rstraszewski commented on GitHub (Nov 25, 2025): same problem

yindo commented

@lizuoqiang commented on GitHub (Nov 25, 2025):

same problem

@lizuoqiang commented on GitHub (Nov 25, 2025): same problem

yindo commented

@softwarezhu commented on GitHub (Nov 25, 2025):

same problem

@softwarezhu commented on GitHub (Nov 25, 2025): same problem

yindo commented

@alitu2025 commented on GitHub (Nov 26, 2025):

same problem

@alitu2025 commented on GitHub (Nov 26, 2025): same problem

yindo commented

@saninmujkic commented on GitHub (Nov 27, 2025):

still same problem. @dosu do you have any news?

@saninmujkic commented on GitHub (Nov 27, 2025): still same problem. @dosu do you have any news?

yindo commented

@pigracing commented on GitHub (Nov 28, 2025):

still same problem. @dosu do you have any news?

@pigracing commented on GitHub (Nov 28, 2025): still same problem. @dosu do you have any news?

yindo commented

@AnoyiX commented on GitHub (Dec 1, 2025):

+1

@AnoyiX commented on GitHub (Dec 1, 2025): +1

yindo commented