langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 20:45:26 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

The workflow log shows successful execution, but the web page keeps displaying "Workflow Process" and fails to show the execution results #7937

New Issue
Closed
opened 2026-02-21 18:23:07 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 18:23:07 -05:00
Owner
Copy Link
Copy Source

Originally created by @poplar-young on GitHub (Jan 31, 2025).

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When executing the GPT-Researcher workflow, the web interface constantly displays "Workflow Process ", but the log shows the workflow has executed successfully and results have been generated.

✔️ Expected Behavior

The web page displays the generated results as complete

❌ Actual Behavior

The web interface keeps displaying "Workflow Process"

Image Image
Originally created by @poplar-young on GitHub (Jan 31, 2025). ### 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.15.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When executing the GPT-Researcher workflow, the web interface constantly displays "Workflow Process ", but the log shows the workflow has executed successfully and results have been generated. ### ✔️ Expected Behavior The web page displays the generated results as complete ### ❌ Actual Behavior The web interface keeps displaying "Workflow Process" <img width="1094" alt="Image" src="https://github.com/user-attachments/assets/17d8b046-9d2c-48ab-a8e2-c9fcdc0553e6" /> <img width="1072" alt="Image" src="https://github.com/user-attachments/assets/79bc67f0-1e1f-4a8c-bfee-46ad01307498" />
yindo closed this issue 2026-02-21 18:23:07 -05:00
yindo commented 2026-02-21 18:23:08 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 31, 2025):

There is a known mechanism in Dify for updating the web interface with workflow execution results. It involves several callback functions that handle different stages of the workflow execution. These callbacks update the state of the workflow and the nodes, which in turn updates the web interface. The onWorkflowFinished callback is particularly important as it updates the workflowRunningData state with the results of the execution, allowing the interface to display the results [1].

Additionally, Dify has specific error handling routines for when the web interface fails to display workflow results. The StatusPanel component handles different statuses such as failed, partial-succeeded, and exception, displaying appropriate messages and links to documentation for further troubleshooting [2].

Given that your workflow log shows successful execution but the web interface does not update, it might be worth checking if the onWorkflowFinished callback is being triggered correctly and if there are any errors being caught by the StatusPanel component. This could help identify if there is an issue with the state update or error handling that is preventing the results from being displayed.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Jan 31, 2025): <!-- Answer --> There is a known mechanism in Dify for updating the web interface with workflow execution results. It involves several callback functions that handle different stages of the workflow execution. These callbacks update the state of the workflow and the nodes, which in turn updates the web interface. The `onWorkflowFinished` callback is particularly important as it updates the `workflowRunningData` state with the results of the execution, allowing the interface to display the results <sup>[[1]](https://github.com/langgenius/dify/blob/main/web/app/components/workflow/hooks/use-workflow-run.ts)</sup>. Additionally, Dify has specific error handling routines for when the web interface fails to display workflow results. The `StatusPanel` component handles different statuses such as `failed`, `partial-succeeded`, and `exception`, displaying appropriate messages and links to documentation for further troubleshooting <sup>[[2]](https://github.com/langgenius/dify/blob/main/web/app/components/workflow/run/status.tsx)</sup>. Given that your workflow log shows successful execution but the web interface does not update, it might be worth checking if the `onWorkflowFinished` callback is being triggered correctly and if there are any errors being caught by the `StatusPanel` component. This could help identify if there is an issue with the state update or error handling that is preventing the results from being displayed. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/0ffe0f1b-2c6f-453a-b31d-1a1e2880ea38?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/0ffe0f1b-2c6f-453a-b31d-1a1e2880ea38?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/0ffe0f1b-2c6f-453a-b31d-1a1e2880ea38?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/0ffe0f1b-2c6f-453a-b31d-1a1e2880ea38?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0ffe0f1b-2c6f-453a-b31d-1a1e2880ea38?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/0ffe0f1b-2c6f-453a-b31d-1a1e2880ea38?feedback_type=other)</sup>
yindo commented 2026-02-21 18:23:08 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jan 31, 2025):

Duplicated https://github.com/langgenius/dify/issues/12230
Duplicated https://github.com/langgenius/dify/issues/7295
The duration of each workflow hit the limit of the timeout. You can edit TEXT_GENERATION_TIMEOUT_MS to get this fixed.

@crazywoola commented on GitHub (Jan 31, 2025): Duplicated https://github.com/langgenius/dify/issues/12230 Duplicated https://github.com/langgenius/dify/issues/7295 The duration of each workflow hit the limit of the timeout. You can edit `TEXT_GENERATION_TIMEOUT_MS` to get this fixed.
yindo commented 2026-02-21 18:23:08 -05:00
Author
Owner
Copy Link
Copy Source

@phoenixor commented on GitHub (May 29, 2025):

Duplicated #12230 Duplicated #7295 The duration of each workflow hit the limit of the timeout. You can edit TEXT_GENERATION_TIMEOUT_MS to get this fixed.

There`s no TEXT_GENERATION_TIMEOUT_MS in .env file with Dify version 0.15.3

@phoenixor commented on GitHub (May 29, 2025): > Duplicated [#12230](https://github.com/langgenius/dify/issues/12230) Duplicated [#7295](https://github.com/langgenius/dify/issues/7295) The duration of each workflow hit the limit of the timeout. You can edit `TEXT_GENERATION_TIMEOUT_MS` to get this fixed. There`s no TEXT_GENERATION_TIMEOUT_MS in .env file with Dify version 0.15.3
yindo commented 2026-02-21 18:23:08 -05:00
Author
Owner
Copy Link
Copy Source

@KleinRose commented on GitHub (Jul 2, 2025):

Duplicated #12230 Duplicated #7295 The duration of each workflow hit the limit of the timeout. You can edit TEXT_GENERATION_TIMEOUT_MS to get this fixed.

There`s no TEXT_GENERATION_TIMEOUT_MS in .env file with Dify version 0.15.3

so why not upgrade your dify.

@KleinRose commented on GitHub (Jul 2, 2025): > > Duplicated [#12230](https://github.com/langgenius/dify/issues/12230) Duplicated [#7295](https://github.com/langgenius/dify/issues/7295) The duration of each workflow hit the limit of the timeout. You can edit `TEXT_GENERATION_TIMEOUT_MS` to get this fixed. > > There`s no TEXT_GENERATION_TIMEOUT_MS in .env file with Dify version 0.15.3 so why not upgrade your dify.
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#7937
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?