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

stopped by user，not the same issue as 8874 #8188

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

Originally created by @JayHsu5 on GitHub (Feb 12, 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.10.2-fix1

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

stopped by user，not the same issue as 8874

https://github.com/langgenius/dify/issues/13556
The same issue also occurs in version 0.15.3.

✔️ Expected Behavior

Execution completed normally.

❌ Actual Behavior

Image

Image

Originally created by @JayHsu5 on GitHub (Feb 12, 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.10.2-fix1 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce stopped by user，not the same issue as 8874 https://github.com/langgenius/dify/issues/13556 The same issue also occurs in version 0.15.3. ### ✔️ Expected Behavior Execution completed normally. ### ❌ Actual Behavior ![Image](https://github.com/user-attachments/assets/eaa1fde8-17e4-4ef0-a862-9cf04e1aa57e) ![Image](https://github.com/user-attachments/assets/96bd8782-1c52-465b-a982-c4927ed76ffa)
yindo added the 🌚 invalid🤔 cant-reproduce labels 2026-02-21 18:24:23 -05:00
yindo closed this issue 2026-02-21 18:24:23 -05:00
yindo commented 2026-02-21 18:24:24 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 12, 2025):

The issue you're experiencing, where the execution is unexpectedly stopped with a "STOP" status, might be related to user-initiated stops in Dify's execution flow. Dify provides specific API endpoints to stop tasks, such as stopChatMessage and stopWorkflow, which are used to halt the execution of chat messages or workflows by specifying the task ID [1][2][3].

If this behavior is not intended and you're sure it's not a user-initiated stop, it could be due to other factors such as configuration settings or potential bugs in the versions you're using. Unfortunately, I couldn't find specific known issues or configurations that might lead to this "STOP" status in the versions 0.10.2-fix1 and 0.15.3. It might be helpful to review any custom configurations or logs for additional clues.

If the issue persists, consider checking for any updates or patches that might address this behavior in newer versions of Dify.

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 12, 2025): <!-- Answer --> The issue you're experiencing, where the execution is unexpectedly stopped with a "STOP" status, might be related to user-initiated stops in Dify's execution flow. Dify provides specific API endpoints to stop tasks, such as `stopChatMessage` and `stopWorkflow`, which are used to halt the execution of chat messages or workflows by specifying the task ID <sup>[[1]](https://github.com/langgenius/dify/blob/main/sdks/nodejs-client/index.js)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/api/controllers/console/app/workflow.py)</sup><sup>[[3]](https://github.com/langgenius/dify/blob/main/sdks/php-client/dify-client.php)</sup>. If this behavior is not intended and you're sure it's not a user-initiated stop, it could be due to other factors such as configuration settings or potential bugs in the versions you're using. Unfortunately, I couldn't find specific known issues or configurations that might lead to this "STOP" status in the versions 0.10.2-fix1 and 0.15.3. It might be helpful to review any custom configurations or logs for additional clues. If the issue persists, consider checking for any updates or patches that might address this behavior in newer versions of Dify. <!-- 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/7acf2de7-fc6f-43bd-bd86-3b3883dbb4f8?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/7acf2de7-fc6f-43bd-bd86-3b3883dbb4f8?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/7acf2de7-fc6f-43bd-bd86-3b3883dbb4f8?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/7acf2de7-fc6f-43bd-bd86-3b3883dbb4f8?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7acf2de7-fc6f-43bd-bd86-3b3883dbb4f8?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/7acf2de7-fc6f-43bd-bd86-3b3883dbb4f8?feedback_type=other) | [Bug Report](https://app.dosu.dev/response-feedback/7acf2de7-fc6f-43bd-bd86-3b3883dbb4f8?feedback_type=bug_report)</sup>
yindo commented 2026-02-21 18:24:24 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 12, 2025):

Can not reproduce.

From the error information, please check APP_MAX_EXECUTION_TIME in the env file.

https://github.com/langgenius/dify/blob/166221d784fb6199050dedf8498397f236734f66/api/core/app/apps/base_app_queue_manager.py#L45-L74

@crazywoola commented on GitHub (Feb 12, 2025): Can not reproduce. From the error information, please check `APP_MAX_EXECUTION_TIME` in the env file. https://github.com/langgenius/dify/blob/166221d784fb6199050dedf8498397f236734f66/api/core/app/apps/base_app_queue_manager.py#L45-L74
yindo commented 2026-02-21 18:24:24 -05:00
Author
Owner
Copy Link
Copy Source

@JayHsu5 commented on GitHub (Feb 12, 2025):

Executing 200 concurrent requests on the local machine will result in this scenario.

@JayHsu5 commented on GitHub (Feb 12, 2025): Executing 200 concurrent requests on the local machine will result in this scenario.
yindo commented 2026-02-21 18:24:24 -05:00
Author
Owner
Copy Link
Copy Source

@JayHsu5 commented on GitHub (Feb 12, 2025):

This is not caused by the APP_MAX_EXECUTION_TIME parameter.

@JayHsu5 commented on GitHub (Feb 12, 2025): This is not caused by the APP_MAX_EXECUTION_TIME parameter.
yindo commented 2026-02-21 18:24:24 -05:00
Author
Owner
Copy Link
Copy Source

@JayHsu5 commented on GitHub (Feb 12, 2025):

@crazywoola

@JayHsu5 commented on GitHub (Feb 12, 2025): @crazywoola
yindo commented 2026-02-21 18:24:24 -05:00
Author
Owner
Copy Link
Copy Source

@JayHsu5 commented on GitHub (Feb 12, 2025):

@tomoyuki28jp @rainchen @iwaim

@JayHsu5 commented on GitHub (Feb 12, 2025): @tomoyuki28jp @rainchen @iwaim
yindo commented 2026-02-21 18:24:24 -05:00
Author
Owner
Copy Link
Copy Source

@woshiyigshuaig commented on GitHub (Apr 27, 2025):

Have you solved it?

@woshiyigshuaig commented on GitHub (Apr 27, 2025): Have you solved it?
yindo commented 2026-02-21 18:24:24 -05:00
Author
Owner
Copy Link
Copy Source

@YLiShu commented on GitHub (Aug 26, 2025):

Executing 200 concurrent requests on the local machine will result in this scenario.

@JayHsu5 Have you solved it? I also encountered a common problem, which occurred when there were 40 concurrent requests on the server.

@YLiShu commented on GitHub (Aug 26, 2025): > Executing 200 concurrent requests on the local machine will result in this scenario. @JayHsu5 Have you solved it? I also encountered a common problem, which occurred when there were 40 concurrent requests on the server.
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 🌚 invalid 🤔 cant-reproduce
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#8188
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?