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

Nodes stay in "Running" state when using "Run this step" #7473

New Issue
Closed
opened 2026-02-21 18:20:46 -05:00 by yindo · 11 comments
yindo commented 2026-02-21 18:20:46 -05:00
Owner
Copy Link
Copy Source

Originally created by @MitraSafarinejad on GitHub (Dec 31, 2024).

Originally assigned to: @laipz8200 on GitHub.

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When testing individual nodes using the "Run this step" feature, the node remains in the "Running" state indefinitely and does not complete. This issue occurs with nodes like Question Classifier, Knowledge Retrieval, and others. However, when running the entire flow in a chatflow, the nodes execute correctly without any issues.

image

✔️ Expected Behavior

The node should complete its execution and display the result or an error message within a reasonable amount of time.

❌ Actual Behavior

The node remains in the "Running" state indefinitely without completing or providing feedback. However, the node works correctly when the entire chatflow is executed.

Originally created by @MitraSafarinejad on GitHub (Dec 31, 2024). Originally assigned to: @laipz8200 on GitHub. ### 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.14.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When testing individual nodes using the "Run this step" feature, the node remains in the "Running" state indefinitely and does not complete. This issue occurs with nodes like Question Classifier, Knowledge Retrieval, and others. However, when running the entire flow in a chatflow, the nodes execute correctly without any issues. ![image](https://github.com/user-attachments/assets/78b3a228-ff7e-4716-8f7a-cc824957ff36) ### ✔️ Expected Behavior The node should complete its execution and display the result or an error message within a reasonable amount of time. ### ❌ Actual Behavior The node remains in the "Running" state indefinitely without completing or providing feedback. However, the node works correctly when the entire chatflow is executed.
yindo added the 🐞 bug label 2026-02-21 18:20:46 -05:00
yindo closed this issue 2026-02-21 18:20:46 -05:00
yindo commented 2026-02-21 18:20:46 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 31, 2024):

I found a similar open issue regarding nodes staying in the "RUNNING" state. The suggested solutions include:

  1. Event Handling: Ensure that event handlers for node execution, such as onNodeStarted and onNodeFinished, are correctly implemented. If these handlers are not triggered, it might cause the node to remain in a "RUNNING" state.

  2. Parallel Node Execution: Check for synchronization issues or deadlocks, especially if your setup involves parallel nodes. Ensure nodes are configured correctly for parallel execution and that there are no dependencies causing a deadlock.

  3. API 'event:ping' Events: Continuous "event:ping" responses might indicate the workflow is stuck in a loop or waiting for a condition that is never met. Ensure all conditions and loops have proper exit criteria.

  4. Logging and Debugging: Use Dify's logging features to gain insights into node executions. Even if no errors are visible, logs might provide clues about where the process is getting stuck.

  5. Version-Specific Issues: Since you're using version 0.14.1, check for any known issues or updates related to this version that might affect node execution [1].

These steps might help identify the root cause of the issue with the "Run this step" feature.

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 (Dec 31, 2024): <!-- Answer --> I found a similar open issue regarding nodes staying in the "RUNNING" state. The suggested solutions include: 1. **Event Handling**: Ensure that event handlers for node execution, such as `onNodeStarted` and `onNodeFinished`, are correctly implemented. If these handlers are not triggered, it might cause the node to remain in a "RUNNING" state. 2. **Parallel Node Execution**: Check for synchronization issues or deadlocks, especially if your setup involves parallel nodes. Ensure nodes are configured correctly for parallel execution and that there are no dependencies causing a deadlock. 3. **API 'event:ping' Events**: Continuous "event:ping" responses might indicate the workflow is stuck in a loop or waiting for a condition that is never met. Ensure all conditions and loops have proper exit criteria. 4. **Logging and Debugging**: Use Dify's logging features to gain insights into node executions. Even if no errors are visible, logs might provide clues about where the process is getting stuck. 5. **Version-Specific Issues**: Since you're using version 0.14.1, check for any known issues or updates related to this version that might affect node execution <sup>[[1]](https://github.com/langgenius/dify/issues/11852)</sup>. These steps might help identify the root cause of the issue with the "Run this step" feature. <!-- 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/ac70a14c-a5d8-4767-88a0-824c9b89642c?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/ac70a14c-a5d8-4767-88a0-824c9b89642c?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/ac70a14c-a5d8-4767-88a0-824c9b89642c?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/ac70a14c-a5d8-4767-88a0-824c9b89642c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ac70a14c-a5d8-4767-88a0-824c9b89642c?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/ac70a14c-a5d8-4767-88a0-824c9b89642c?feedback_type=other)</sup>
yindo commented 2026-02-21 18:20:46 -05:00
Author
Owner
Copy Link
Copy Source

@MitraSafarinejad commented on GitHub (Jan 2, 2025):

I have discovered that this issue causes an even more critical problem. When I use the "Run this step" feature, and the node stays in the "Running" state, it continuously calls APIs, leading to infinite API requests. For example, when testing an LLM Node, it keeps sending requests to the OpenAI API without stopping, resulting in significant financial costs. This makes the issue highly urgent and requires immediate attention. Please prioritize this as it is causing substantial damage.
@crazywoola

@MitraSafarinejad commented on GitHub (Jan 2, 2025): I have discovered that this issue causes an even more critical problem. When I use the "Run this step" feature, and the node stays in the "Running" state, it continuously calls APIs, leading to infinite API requests. For example, when testing an LLM Node, it keeps sending requests to the OpenAI API without stopping, resulting in significant financial costs. This makes the issue highly urgent and requires immediate attention. Please prioritize this as it is causing substantial damage. @crazywoola
yindo commented 2026-02-21 18:20:46 -05:00
Author
Owner
Copy Link
Copy Source

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

@MitraSafarinejad We will take a look at this ASAP.
Can you attach a screenshot or the DSL of the workflow?
I am not able to see the configuration of the node here. I can not reproduce this problem in our cloud env.

@crazywoola commented on GitHub (Jan 2, 2025): @MitraSafarinejad We will take a look at this ASAP. Can you attach a screenshot or the DSL of the workflow? I am not able to see the configuration of the node here. I can not reproduce this problem in our cloud env.
yindo commented 2026-02-21 18:20:46 -05:00
Author
Owner
Copy Link
Copy Source

@MitraSafarinejad commented on GitHub (Jan 2, 2025):

@crazywoola Thank you for your attention to this issue.

Here are the nodes and the chatflow I am using. It’s a simple flow, so I hope this helps you understand the configuration and reproduce the problem. Additionally, I want to note that I am running the system using Docker, not the cloud environment.

Please let me know if you need any additional details or further clarification.

Looking forward to your updates!

image
image
image
image

@MitraSafarinejad commented on GitHub (Jan 2, 2025): @crazywoola Thank you for your attention to this issue. Here are the nodes and the chatflow I am using. It’s a simple flow, so I hope this helps you understand the configuration and reproduce the problem. Additionally, I want to note that I am running the system using Docker, not the cloud environment. Please let me know if you need any additional details or further clarification. Looking forward to your updates! ![image](https://github.com/user-attachments/assets/4167d8ad-7e82-42d7-96d3-ebd5a9232fe1) ![image](https://github.com/user-attachments/assets/bd5cdc5b-02a7-4faa-8173-7196aec44df2) ![image](https://github.com/user-attachments/assets/7be07c33-f1de-44e4-bfa6-068536119c24) ![image](https://github.com/user-attachments/assets/3e1d590b-c31c-4bca-a9ff-78906b7488a7)
yindo commented 2026-02-21 18:20:46 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (Jan 2, 2025):

image

Hi @MitraSafarinejad! I tried to create a similar chatflow with you in version 0.14.1, using the same model, but I can't reproduce this issue. Could you provide more information? Maybe you could copy the API logs from your Docker container when this issue occurs.

@laipz8200 commented on GitHub (Jan 2, 2025): <img width="1124" alt="image" src="https://github.com/user-attachments/assets/3bd68544-15b7-4a62-b7a4-cf22983bb8ee" /> Hi @MitraSafarinejad! I tried to create a similar chatflow with you in version 0.14.1, using the same model, but I can't reproduce this issue. Could you provide more information? Maybe you could copy the API logs from your Docker container when this issue occurs.
yindo commented 2026-02-21 18:20:46 -05:00
Author
Owner
Copy Link
Copy Source

@MitraSafarinejad commented on GitHub (Jan 4, 2025):

Hi @laipz8200,

Thanks for following up! Below, I’ve included the logs generated when I ran the LLM nodes, along with the DSL file exported from my chatflow for your reference.

log.txt
dsl.txt

@MitraSafarinejad commented on GitHub (Jan 4, 2025): Hi @laipz8200, Thanks for following up! Below, I’ve included the logs generated when I ran the LLM nodes, along with the DSL file exported from my chatflow for your reference. [log.txt](https://github.com/user-attachments/files/18306354/log.txt) [dsl.txt](https://github.com/user-attachments/files/18306358/dsl.txt)
yindo commented 2026-02-21 18:20:47 -05:00
Author
Owner
Copy Link
Copy Source

@MitraSafarinejad commented on GitHub (Jan 11, 2025):

hello,
I updated my dify version to 0.14.2 and the problem does not exist anymore

@MitraSafarinejad commented on GitHub (Jan 11, 2025): hello, I updated my dify version to 0.14.2 and the problem does not exist anymore
yindo commented 2026-02-21 18:20:47 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (Jan 13, 2025):

Hi @MitraSafarinejad. Thank you for your feedback!

@laipz8200 commented on GitHub (Jan 13, 2025): Hi @MitraSafarinejad. Thank you for your feedback!
yindo commented 2026-02-21 18:20:47 -05:00
Author
Owner
Copy Link
Copy Source

@HanXM715 commented on GitHub (Apr 2, 2025):

@laipz8200 @crazywoola My current version is 0.14.2 and I have a similar problem, also calling the API constantly, resulting in infinite API requests

@HanXM715 commented on GitHub (Apr 2, 2025): @laipz8200 @crazywoola My current version is 0.14.2 and I have a similar problem, also calling the API constantly, resulting in infinite API requests
yindo commented 2026-02-21 18:20:47 -05:00
Author
Owner
Copy Link
Copy Source

@HanXM715 commented on GitHub (Apr 2, 2025):

Image

Image

@HanXM715 commented on GitHub (Apr 2, 2025): ![Image](https://github.com/user-attachments/assets/6fd7ef48-7260-47ac-9364-3c17eec87194) ![Image](https://github.com/user-attachments/assets/5d67cfb5-3681-4699-929d-352f91937931)
yindo commented 2026-02-21 18:20:47 -05:00
Author
Owner
Copy Link
Copy Source

@tkysi-mi commented on GitHub (Jul 8, 2025):

I am encountering a similar issue in Cloud version right now...

Image
@tkysi-mi commented on GitHub (Jul 8, 2025): I am encountering a similar issue in Cloud version right now... <img width="891" height="1670" alt="Image" src="https://github.com/user-attachments/assets/55c0a774-04b2-4a1f-bc75-fc7babd03e8f" />
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#7473
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?