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

Failed to invoke tool:timed out #13860

New Issue
Closed
opened 2026-02-21 19:14:15 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 19:14:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @Panic-Monster on GitHub (May 14, 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.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Firstly, publish a workflow as a tool, and use another workflow to call the workflow that has been published as a tool. If it runs for more than 10 minutes on this workflow node that has been published as a tool, it will report a "Failed
to invoke tool : timed out"

Image

✔️ Expected Behavior

I hope someone can solve how to increase the timeout period

❌ Actual Behavior

No response

Originally created by @Panic-Monster on GitHub (May 14, 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.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Firstly, publish a workflow as a tool, and use another workflow to call the workflow that has been published as a tool. If it runs for more than 10 minutes on this workflow node that has been published as a tool, it will report a "Failed to invoke tool : timed out" ![Image](https://github.com/user-attachments/assets/c0d965a1-5292-489a-b619-382cb2e34297) ### ✔️ Expected Behavior I hope someone can solve how to increase the timeout period ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:14:15 -05:00
yindo closed this issue 2026-02-21 19:14:15 -05:00
yindo commented 2026-02-21 19:14:15 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 14, 2025):

Hello @Panic-Monster! I'm Dosu, your friendly bot here to help you with bugs, questions, and anything else you might need while waiting for a human maintainer. Let's tackle this issue together!

To address the timeout issue you're experiencing with tool invocation in your self-hosted Dify version 0.15.0 using Docker, you can try the following steps:

  1. Volume Mapping: Add the volume mapping "/volumes/sandbox/conf:/conf" in your docker-compose.yaml file.

  2. Update Configuration: Modify the config.yaml file to include the appropriate allowed_syscalls range (0-500).

  3. Extend Timeout Period: Add the following configuration to your docker-compose.yaml to extend the timeout period:

    plugin_daemon:
  environment:
    PYTHON_ENV_INIT_TIMEOUT: 320
    GUNICORN_TIMEOUT: 360

  4. Correct Image Version: Ensure you are using the correct image version for the plugin daemon to avoid potential issues:

    plugin_daemon:
  image: langgenius/dify-plugin-daemon:e0672c3c1a6451437e8f4b63b260c8b0863c9c80-local

These steps should help resolve the timeout error you're encountering. If you face an 'operation not permitted' error after making these changes, consult the dify-sandbox FAQ documentation for additional configuration requirements [1].

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (May 14, 2025): <!-- Greeting --> Hello @Panic-Monster! I'm [Dosu](https://dosu.dev), your friendly bot here to help you with bugs, questions, and anything else you might need while waiting for a human maintainer. Let's tackle this issue together! <!-- Answer --> To address the timeout issue you're experiencing with tool invocation in your self-hosted Dify version 0.15.0 using Docker, you can try the following steps: 1. **Volume Mapping**: Add the volume mapping `"/volumes/sandbox/conf:/conf"` in your `docker-compose.yaml` file. 2. **Update Configuration**: Modify the `config.yaml` file to include the appropriate `allowed_syscalls` range (0-500). 3. **Extend Timeout Period**: Add the following configuration to your `docker-compose.yaml` to extend the timeout period: ```yaml plugin_daemon: environment: PYTHON_ENV_INIT_TIMEOUT: 320 GUNICORN_TIMEOUT: 360 ``` 4. **Correct Image Version**: Ensure you are using the correct image version for the plugin daemon to avoid potential issues: ```yaml plugin_daemon: image: langgenius/dify-plugin-daemon:e0672c3c1a6451437e8f4b63b260c8b0863c9c80-local ``` These steps should help resolve the timeout error you're encountering. If you face an 'operation not permitted' error after making these changes, consult the dify-sandbox FAQ documentation for additional configuration requirements <sup>[[1]](https://github.com/langgenius/dify/issues/15817)</sup>. <!-- 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/edf76111-2acf-4a7d-b71f-defce4f82b31?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/edf76111-2acf-4a7d-b71f-defce4f82b31?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/edf76111-2acf-4a7d-b71f-defce4f82b31?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/edf76111-2acf-4a7d-b71f-defce4f82b31?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/edf76111-2acf-4a7d-b71f-defce4f82b31?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/edf76111-2acf-4a7d-b71f-defce4f82b31?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/edf76111-2acf-4a7d-b71f-defce4f82b31?feedback_type=other)</sup>
yindo commented 2026-02-21 19:14:15 -05:00
Author
Owner
Copy Link
Copy Source

@Panic-Monster commented on GitHub (May 14, 2025):

Can you be more detailed? I didn't understand the second step

@Panic-Monster commented on GitHub (May 14, 2025): Can you be more detailed? I didn't understand the second step
yindo commented 2026-02-21 19:14:15 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (May 14, 2025):

This is an outdated version, please upgrade to the latest version.

@crazywoola commented on GitHub (May 14, 2025): This is an outdated version, please upgrade to the latest version.
yindo commented 2026-02-21 19:14:15 -05:00
Author
Owner
Copy Link
Copy Source

@Panic-Monster commented on GitHub (May 14, 2025):

sry，It's not easy for us to update the new version here，Is there any way to solve it in the current version

@Panic-Monster commented on GitHub (May 14, 2025): sry，It's not easy for us to update the new version here，Is there any way to solve it in the current version
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#13860
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?