Timeout Issue with HTTP Requests or Custom Tool API Calls in Workflows #3496

Closed
opened 2026-02-21 17:58:31 -05:00 by yindo · 0 comments
Owner

Originally created by @opsvr202 on GitHub (May 21, 2024).

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).
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.8

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Add one or more HTTP request nodes or custom tool nodes in the workflow designer.
  2. Save and publish the workflow.
  3. Invoke the workflow using the API.
  4. Observe if the API call times out after one minute and returns the aforementioned error message.

✔️ Expected Behavior

When invoking a workflow through the API, even if it contains HTTP request or custom tool nodes, it should complete as expected without timing out.

Actual Behavior

When invoking a workflow through the API, if the workflow contains HTTP request or custom tool nodes, the interface times out after approximately one minute and returns an error message: "Node <node_name> run failed: Failed to invoke tool: timed out."

Originally created by @opsvr202 on GitHub (May 21, 2024). ### 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] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.8 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. Add one or more HTTP request nodes or custom tool nodes in the workflow designer. 2. Save and publish the workflow. 3. Invoke the workflow using the API. 4. Observe if the API call times out after one minute and returns the aforementioned error message. ### ✔️ Expected Behavior When invoking a workflow through the API, even if it contains HTTP request or custom tool nodes, it should complete as expected without timing out. ### ❌ Actual Behavior When invoking a workflow through the API, if the workflow contains HTTP request or custom tool nodes, the interface times out after approximately one minute and returns an error message: "Node <node_name> run failed: Failed to invoke tool: timed out."
yindo added the 🐞 bug label 2026-02-21 17:58:31 -05:00
yindo closed this issue 2026-02-21 17:58:31 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#3496