langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 19:50:06 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Long Loading Time when Starting the Chatflow on Cloud Version #21539

New Issue
Open
opened 2026-02-21 20:13:04 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:13:04 -05:00
Owner
Copy Link
Copy Source

Originally created by @shenjiekoh on GitHub (Jan 9, 2026).

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

Cloud or Self Hosted

Cloud

Steps to reproduce

Issue Description

There is a significant long loading time (latency) before running Start node when I send a message to the chatflow.

Details

Long Loading Time

When sending a message to the chatflow, there is a significant delay before the Start node begins execution.

Image

I have performed two runs and here are the execution results:

Image Image

Here is an actual tracing result of one run:

Image

Based on tracing data, I believe most of the latency occurs before the Start node is triggered, which is unexpected. The expected time should be within 3s in this case.

Reproduction Steps

  1. Open the chatflow.
  2. Send a message to the chatflow.
  3. Observe the loading period before the Start node runs.

Additional Info

  • The chatflow contains 100~120 nodes.
  • No external API calls are made before the Start node.
  • The issue is reproducible across multiple runs.

✔️ Expected Behavior

The chatflow will start processing the message immediately or with very short latency once it received a message.

❌ Actual Behavior

The chatflow suffers from a long loading time after it received a message.

Originally created by @shenjiekoh on GitHub (Jan 9, 2026). ### 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.11.2 ### Cloud or Self Hosted Cloud ### Steps to reproduce ### Issue Description There is a significant long loading time (latency) before running **Start** node when I send a message to the chatflow. ### Details #### Long Loading Time When sending a message to the chatflow, there is a significant delay before the **Start** node begins execution. <img width="436" height="228" alt="Image" src="https://github.com/user-attachments/assets/35b7026a-8d9c-4acb-bd1b-02f4e2afa96f" /> I have performed two runs and here are the execution results: <img width="377" height="331" alt="Image" src="https://github.com/user-attachments/assets/cb54eb8b-8ab7-41ca-a5e8-fcccd3e1bddd" /> <img width="379" height="332" alt="Image" src="https://github.com/user-attachments/assets/74b6838c-b034-4931-9a2f-0c5e4057297e" /> Here is an actual tracing result of one run: <img width="393" height="487" alt="Image" src="https://github.com/user-attachments/assets/6bdcc42f-70cc-47a6-b031-5f5f89b5b6e9" /> Based on tracing data, I believe most of the latency occurs **before** the Start node is triggered, which is unexpected. The expected time should be within 3s in this case. #### Reproduction Steps 1. Open the chatflow. 2. Send a message to the chatflow. 3. Observe the loading period before the Start node runs. #### Additional Info - The chatflow contains 100~120 nodes. - No external API calls are made before the Start node. - The issue is reproducible across multiple runs. ### ✔️ Expected Behavior The chatflow will start processing the message immediately or with very short latency once it received a message. ### ❌ Actual Behavior The chatflow suffers from a long loading time after it received a message.
yindo added the 🐞 bugstalecloud labels 2026-02-21 20:13:04 -05:00
yindo commented 2026-02-21 20:13:04 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 9, 2026):

Hi @shenjiekoh! I'm Dosu and I’m helping the dify team.

This is a known performance issue with large chatflows (100–120 nodes) on Dify Cloud v1.11.2. Most of the latency before the Start node runs comes from initialization steps like conversation/message retrieval, variable loading and syncing from the database, and full workflow graph setup. These steps scale poorly with large node counts and there’s currently no explicit optimization or caching for big workflows, which leads to the delays you’re seeing. Multiple users have reported similar problems, and while a fix improved self-hosted deployments, it hasn’t been confirmed for cloud yet—users continue to report lag on cloud even after the fix was merged for self-hosted instances. For now, the best workarounds are to reduce the number of nodes in a workflow or split large flows, and keep an eye on GitHub issues and release notes for updates on cloud-side performance improvements for large workflows.
Reference 1
Reference 2
Reference 3

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 9, 2026): <!-- Greeting --> Hi @shenjiekoh! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This is a known performance issue with large chatflows (100–120 nodes) on Dify Cloud v1.11.2. Most of the latency before the Start node runs comes from initialization steps like conversation/message retrieval, variable loading and syncing from the database, and full workflow graph setup. These steps scale poorly with large node counts and there’s currently no explicit optimization or caching for big workflows, which leads to the delays you’re seeing. Multiple users have reported similar problems, and while a fix improved self-hosted deployments, it hasn’t been confirmed for cloud yet—users continue to report lag on cloud even after the fix was merged for self-hosted instances. For now, the best workarounds are to reduce the number of nodes in a workflow or split large flows, and keep an eye on GitHub issues and release notes for updates on cloud-side performance improvements for large workflows. [Reference 1](https://github.com/langgenius/dify/issues/30196) [Reference 2](https://github.com/langgenius/dify/issues/28245) [Reference 3](https://github.com/langgenius/dify/blob/98df99b0ca2f13db64eba18e37489db5c534eadd/api/core/app/apps/advanced_chat/app_runner.py#L49-L346) <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/5ef48035-ea56-4a7d-a3b1-a90797cf7be1?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5ef48035-ea56-4a7d-a3b1-a90797cf7be1?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5ef48035-ea56-4a7d-a3b1-a90797cf7be1?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5ef48035-ea56-4a7d-a3b1-a90797cf7be1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5ef48035-ea56-4a7d-a3b1-a90797cf7be1?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5ef48035-ea56-4a7d-a3b1-a90797cf7be1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5ef48035-ea56-4a7d-a3b1-a90797cf7be1?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20is%20a%20known%20performance%20issue%20with%20large%20chatflows%20%28100%E2%80%93120%20nodes%29%20on%20Dify%20Cloud%20v1.11.2.%20Most%20of%20the%20latency%20before%20the%20Start%20node%20runs%20comes%20from%20initialization%20steps%20like%20conversation/message%20retrieval%2C%20variable%20loading%20and%20syncing%20from%20the%20database%2C%20and%20full%20workflow%20graph%20setup.%20These%20steps%20scale%20poorly%20with%20large%20node%20counts%20and%20there%E2%80%99s%20currently%20no%20explicit%20optimization%20or%20caching%20for%20big%20workflows%2C%20which%20leads%20to%20the%20delays%20you%E2%80%99re%20seeing.%20Multiple%20users%20have%20reported%20similar%20problems%2C%20and%20while%20a%20fix%20improved%20self-hosted%20deployments%2C%20it%20hasn%E2%80%99t%20been%20confirmed%20for%20cloud%20yet%E2%80%94users%20continue%20to%20report%20lag%20on%20cloud%20even%20after%20the%20fix%20was%20merged%20for%20self-hosted%20instances.%20For%20now%2C%20the%20best%20workarounds%20are%20to%20reduce%20the%20number%20of%20nodes%20in%20a%20workflow%20or%20split%20large%20flows%2C%20and%20keep%20an%20eye%20on%20GitHub%20issues%20and%20release%20notes%20for%20updates%20on%20cloud-side%20performance%20improvements%20for%20large%20workflows.%20%20%0A%5BReference%201%5D%28https%3A//github.com/langgenius/dify/issues/30196%29%20%20%0A%5BReference%202%5D%28https%3A//github.com/langgenius/dify/issues/28245%29%20%20%0A%5BReference%203%5D%28https%3A//github.com/langgenius/dify/blob/98df99b0ca2f13db64eba18e37489db5c534eadd/api/core/app/apps/advanced_chat/app_runner.py%23L49-L346%29)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/30772)
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 cloud stale 🐞 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#21539
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?