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

The invocation time of the HTTP Request node is occasionally abnormal. #19229

New Issue
Open
opened 2026-02-21 19:57:17 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 19:57:17 -05:00
Owner
Copy Link
Copy Source

Originally created by @0sengseng0 on GitHub (Oct 14, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.8.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Question

As shown in the figure below, a simple HTTP call is made. Occasionally, there will be issues with abnormal call times, and this occurs approximately once every 10 calls.
Image

An extremely important point is that the abnormal time for each call is always 16 seconds plus the normal response time of this interface.

So where did this 16 seconds come from? I couldn't find any relevant configuration in the .env file.
I tried different interfaces and conducted concurrent tests on these interfaces separately. I'm very certain that it's not a problem with the interfaces.

Config

I attempted to modify some of the configurations in the .env file, but the problem still persists.

SERVER_WORKER_AMOUNT=2
SERVER_WORKER_CONNECTIONS=30
SQLALCHEMY_POOL_SIZE=60
POSTGRES_MAX_CONNECTIONS=300

✔️ Expected Behavior

The normal response time of this interface is less than 1 second. I need it to function properly.

❌ Actual Behavior

In fact, there is an additional 16-second delay.

Originally created by @0sengseng0 on GitHub (Oct 14, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.8.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce # Question As shown in the figure below, a simple HTTP call is made. Occasionally, there will be issues with abnormal call times, and this occurs approximately once every 10 calls. <img width="1536" height="462" alt="Image" src="https://github.com/user-attachments/assets/5b5385c8-3e8c-4f1f-a50e-244ec57d7427" /> An extremely important point is that the abnormal time for each call is always 16 seconds plus the normal response time of this interface. So where did this 16 seconds come from? I couldn't find any relevant configuration in the .env file. I tried different interfaces and conducted concurrent tests on these interfaces separately. I'm very certain that it's not a problem with the interfaces. # Config I attempted to modify some of the configurations in the .env file, but the problem still persists. ``` SERVER_WORKER_AMOUNT=2 SERVER_WORKER_CONNECTIONS=30 SQLALCHEMY_POOL_SIZE=60 POSTGRES_MAX_CONNECTIONS=300 ``` ### ✔️ Expected Behavior The normal response time of this interface is less than 1 second. I need it to function properly. ### ❌ Actual Behavior In fact, there is an additional 16-second delay.
yindo added the 🐞 bug label 2026-02-21 19:57:17 -05:00
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#19229
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?