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

Iternal Error #20773

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

Originally created by @kazuhattori-ai on GitHub (Dec 3, 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.10.1

Cloud or Self Hosted

Cloud

Steps to reproduce

When I click the “Workflow” tab, no apps are shown and a red banner “Internal Server Error” appears.
Other app types (Chatflow, Chatbot) are displayed normally.
This happens in all browsers.
Could you check my workspace and remove or fix the broken workflow app that is causing the 500 error?

✔️ Expected Behavior

I want to check “Workflow” apps.

❌ Actual Behavior

No response

Originally created by @kazuhattori-ai on GitHub (Dec 3, 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.10.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce When I click the “Workflow” tab, no apps are shown and a red banner “Internal Server Error” appears. Other app types (Chatflow, Chatbot) are displayed normally. This happens in all browsers. Could you check my workspace and remove or fix the broken workflow app that is causing the 500 error? ### ✔️ Expected Behavior I want to check “Workflow” apps. ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 20:08:54 -05:00
yindo commented 2026-02-21 20:08:54 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi @kazuhattori-ai! I'm Dosu and I’m helping the dify team.

The 500 Internal Server Error on the Workflow tab is most likely caused by a backend issue with workflow app data, validation/model initialization, or missing context providers. Recent fixes have addressed similar problems, including a validation error in workflow entities and improved error handling for workflow nodes and UI context providers (PR #28636, PR #28985). If your cloud deployment hasn't received these updates yet, they may resolve the error once applied.

If the error persists, enable DEBUG logging and check backend logs for details when you access the Workflow tab—look for validation errors, missing models, or corrupted workflow drafts. If you can share the backend error trace or details about recently created/edited workflow apps, maintainers can help pinpoint and remove or fix the broken app.

Manual removal of a broken workflow app is possible via the delete function in the backend, which triggers asynchronous cleanup of related data. If you have admin access, you can try deleting the problematic workflow app to restore normal operation.

Let me know if you can provide error logs or more details about the affected workflow apps—happy to help further!

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 3, 2025): <!-- Greeting --> Hi @kazuhattori-ai! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The 500 Internal Server Error on the Workflow tab is most likely caused by a backend issue with workflow app data, validation/model initialization, or missing context providers. Recent fixes have addressed similar problems, including a validation error in workflow entities and improved error handling for workflow nodes and UI context providers ([PR #28636](https://github.com/langgenius/dify/pull/28636), [PR #28985](https://github.com/langgenius/dify/pull/28985)). If your cloud deployment hasn't received these updates yet, they may resolve the error once applied. If the error persists, enable DEBUG logging and check backend logs for details when you access the Workflow tab—look for validation errors, missing models, or corrupted workflow drafts. If you can share the backend error trace or details about recently created/edited workflow apps, maintainers can help pinpoint and remove or fix the broken app. Manual removal of a broken workflow app is possible via the delete function in the backend, which triggers asynchronous cleanup of related data. If you have admin access, you can try deleting the problematic workflow app to restore normal operation. Let me know if you can provide error logs or more details about the affected workflow apps—happy to help further! <!-- 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/445ccf4e-8dbd-4c5c-a0fa-22c8b2dd7a2f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/445ccf4e-8dbd-4c5c-a0fa-22c8b2dd7a2f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/445ccf4e-8dbd-4c5c-a0fa-22c8b2dd7a2f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/445ccf4e-8dbd-4c5c-a0fa-22c8b2dd7a2f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/445ccf4e-8dbd-4c5c-a0fa-22c8b2dd7a2f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/445ccf4e-8dbd-4c5c-a0fa-22c8b2dd7a2f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/445ccf4e-8dbd-4c5c-a0fa-22c8b2dd7a2f?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%20500%20Internal%20Server%20Error%20on%20the%20Workflow%20tab%20is%20most%20likely%20caused%20by%20a%20backend%20issue%20with%20workflow%20app%20data%2C%20validation/model%20initialization%2C%20or%20missing%20context%20providers.%20Recent%20fixes%20have%20addressed%20similar%20problems%2C%20including%20a%20validation%20error%20in%20workflow%20entities%20and%20improved%20error%20handling%20for%20workflow%20nodes%20and%20UI%20context%20providers%20%28%5BPR%20%2328636%5D%28https%3A//github.com/langgenius/dify/pull/28636%29%2C%20%5BPR%20%2328985%5D%28https%3A//github.com/langgenius/dify/pull/28985%29%29.%20If%20your%20cloud%20deployment%20hasn%27t%20received%20these%20updates%20yet%2C%20they%20may%20resolve%20the%20error%20once%20applied.%0A%0AIf%20the%20error%20persists%2C%20enable%20DEBUG%20logging%20and%20check%20backend%20logs%20for%20details%20when%20you%20access%20the%20Workflow%20tab%E2%80%94look%20for%20validation%20errors%2C%20missing%20models%2C%20or%20corrupted%20workflow%20drafts.%20If%20you%20can%20share%20the%20backend%20error%20trace%20or%20details%20about%20recently%20created/edited%20workflow%20apps%2C%20maintainers%20can%20help%20pinpoint%20and%20remove%20or%20fix%20the%20broken%20app.%0A%0AManual%20removal%20of%20a%20broken%20workflow%20app%20is%20possible%20via%20the%20delete%20function%20in%20the%20backend%2C%20which%20triggers%20asynchronous%20cleanup%20of%20related%20data.%20If%20you%20have%20admin%20access%2C%20you%20can%20try%20deleting%20the%20problematic%20workflow%20app%20to%20restore%20normal%20operation.%0A%0ALet%20me%20know%20if%20you%20can%20provide%20error%20logs%20or%20more%20details%20about%20the%20affected%20workflow%20apps%E2%80%94happy%20to%20help%20further%21)&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/29093)
yindo commented 2026-02-21 20:08:54 -05:00
Author
Owner
Copy Link
Copy Source

@kazuhattori-ai commented on GitHub (Dec 3, 2025):

@dosu.

I don't know which workflow has the problem because I can't see the workflow at all. How can I see the workflow with the problem?

@kazuhattori-ai commented on GitHub (Dec 3, 2025): [@dosu](https://go.dosu.dev/dosubot). I don't know which workflow has the problem because I can't see the workflow at all. How can I see the workflow with the problem?
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
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#20773
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?