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

Bug: has_more always false in conversation variables pagination #17074

New Issue
Closed
opened 2026-02-21 19:30:58 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 19:30:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @hyongtao-code on GitHub (Sep 10, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactoring, 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.

Description

Version: cloud

Summary

When calling the GET /conversations/{conversation_id}/variables API, the has_more field is always returned as false, even when the number of variables exceeds the specified limit.

Steps to Reproduce

  1. Create a conversation with 11 variables.
Image
  1. Call the API with limit=20:
GET /v1/conversations/{conversation_id}/variables?user=abc-123&limit=20
  1. Call the API with limit=10:
GET /v1/conversations/{conversation_id}/variables?user=abc-123&limit=10
Image

Expected behavior

has_more should be true when there are more variables available beyond the current page size. For example, with 11 variables total and limit=10, the response should include 10 items with has_more: true.

Motivation

No response

Additional Context

No response

Originally created by @hyongtao-code on GitHub (Sep 10, 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 refactoring, 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. ### Description Version: cloud ### Summary When calling the GET /conversations/{conversation_id}/variables API, the has_more field is always returned as false, even when the number of variables exceeds the specified limit. ### Steps to Reproduce 1. Create a conversation with 11 variables. <img width="848" height="1312" alt="Image" src="https://github.com/user-attachments/assets/ef7d86e2-7bb2-446f-830d-b115ccc40946" /> 2. Call the API with `limit=20`: ``` bash GET /v1/conversations/{conversation_id}/variables?user=abc-123&limit=20 ``` 3. Call the API with `limit=10`: ``` bash GET /v1/conversations/{conversation_id}/variables?user=abc-123&limit=10 ``` <img width="1650" height="1238" alt="Image" src="https://github.com/user-attachments/assets/140293d2-7ea4-4947-81e0-9cb458981075" /> ### Expected behavior has_more should be true when there are more variables available beyond the current page size. For example, with 11 variables total and limit=10, the response should include 10 items with has_more: true. ### Motivation _No response_ ### Additional Context _No response_
yindo added the 🐞 bugrefactor labels 2026-02-21 19:30:58 -05:00
yindo closed this issue 2026-02-21 19:30:58 -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 refactor 🐞 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#17074
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?