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

Infinite messages call #20113

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

Originally created by @DavideDelbianco on GitHub (Nov 4, 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.9.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

have a 40 messages conversation with a chatflow
go to the logs
open the conversation log
scroll just one time

✔️ Expected Behavior

The "fetch more" should happen when the top of the chat is reached

❌ Actual Behavior

the "fetch more" happens multiple time after scrolling just a few pixels and once there's no more history to load, it keeps calling the fetch

Originally created by @DavideDelbianco on GitHub (Nov 4, 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.9.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce have a 40 messages conversation with a chatflow go to the logs open the conversation log scroll just one time ### ✔️ Expected Behavior The "fetch more" should happen when the top of the chat is reached ### ❌ Actual Behavior the "fetch more" happens multiple time after scrolling just a few pixels and once there's no more history to load, it keeps calling the fetch
yindo added the 🐞 bug label 2026-02-21 20:05:54 -05:00
yindo closed this issue 2026-02-21 20:05:54 -05:00
yindo commented 2026-02-21 20:05:55 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 4, 2025):

This is a known issue with the scroll event handling in the chat log UI. The frontend uses a scroll listener that triggers "fetch more" when you scroll near the top, with a throttle to limit calls. However, if the backend keeps returning has_more: true but no new data, or if the frontend doesn't update the hasMore state correctly, it can cause repeated fetches even when there's no more history to load. There is also retry logic that can trigger additional fetches if no new unique messages are found, which may contribute to the problem.

A recent update has improved the infinite scroll observer's responsiveness and event detection, which should help prevent repeated fetch calls when no more data is available. If possible, consider updating to the latest version where this fix is included. For reference, see the merged PR that addresses this frontend issue here.

If you need a workaround, double-check that your backend correctly sets has_more: false when there are no more messages, and ensure your frontend is running the latest code with these improvements.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 4, 2025): <!-- Answer --> This is a known issue with the scroll event handling in the chat log UI. The frontend uses a scroll listener that triggers "fetch more" when you scroll near the top, with a throttle to limit calls. However, if the backend keeps returning `has_more: true` but no new data, or if the frontend doesn't update the `hasMore` state correctly, it can cause repeated fetches even when there's no more history to load. There is also retry logic that can trigger additional fetches if no new unique messages are found, which may contribute to the problem. A recent update has improved the infinite scroll observer's responsiveness and event detection, which should help prevent repeated fetch calls when no more data is available. If possible, consider updating to the latest version where this fix is included. For reference, see the merged PR that addresses this frontend issue [here](https://github.com/langgenius/dify/pull/27546). If you need a workaround, double-check that your backend correctly sets `has_more: false` when there are no more messages, and ensure your frontend is running the latest code with these improvements. <!-- 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/8a85c792-b884-4c4e-ad11-ab8dad50915b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/8a85c792-b884-4c4e-ad11-ab8dad50915b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/8a85c792-b884-4c4e-ad11-ab8dad50915b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/8a85c792-b884-4c4e-ad11-ab8dad50915b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8a85c792-b884-4c4e-ad11-ab8dad50915b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/8a85c792-b884-4c4e-ad11-ab8dad50915b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8a85c792-b884-4c4e-ad11-ab8dad50915b?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&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/27804)
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#20113
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?