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

same problem, different knowledge base recalls #16432

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

Originally created by @3099749306 on GitHub (Aug 25, 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.3.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The same question can be answered correctly in the Dify intelligent agent preview, but after integrating with the business, the documents recalled by the knowledge base will always be missing item 3. I have confirmed that Project 3 exists in relation to the knowledge base, but I am confused and frustrated

Image Image

✔️ Expected Behavior

resolve my problem，or tell me why

❌ Actual Behavior

No response

Originally created by @3099749306 on GitHub (Aug 25, 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.3.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The same question can be answered correctly in the Dify intelligent agent preview, but after integrating with the business, the documents recalled by the knowledge base will always be missing item 3. I have confirmed that Project 3 exists in relation to the knowledge base, but I am confused and frustrated <img width="807" height="1251" alt="Image" src="https://github.com/user-attachments/assets/dbdcd9c2-bef7-4640-855b-d3a046572d89" /> <img width="1152" height="1011" alt="Image" src="https://github.com/user-attachments/assets/5b9fa3d3-69f8-41e2-9b44-db6686e4568b" /> ### ✔️ Expected Behavior resolve my problem，or tell me why ### ❌ Actual Behavior _No response_
yindo added the 🐞 bugoutdated labels 2026-02-21 19:26:05 -05:00
yindo closed this issue 2026-02-21 19:26:05 -05:00
yindo commented 2026-02-21 19:26:05 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 25, 2025):

The most common reasons for inconsistent knowledge base recall between the agent preview and your business integration are differences in document status, permissions, user/tenant context, and API parameters. Dify filters out documents that are disabled, not fully indexed, or archived, and also enforces strict permission checks at both the dataset and document level. If the integration context (API token, user role, or tenant) differs from the preview, or if the document's status isn't "enabled" and "indexing completed," some items (like your missing Project 3) won't be recalled in the integrated environment—even if they appear in the preview. Recent changes also mean that search and recall now depend on live API data and parameters like page, limit, and keyword, which can further affect results if not matched between environments [source] [source].

To troubleshoot: check that Project 3 is enabled, not archived, and fully indexed; verify that the integration uses the same user/tenant context and permissions as the preview; and compare the API requests and parameters (including pagination and filters) used in both environments. If the issue persists, try querying the document list via the API directly to confirm its visibility and status.

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 (Aug 25, 2025): <!-- Answer --> The most common reasons for inconsistent knowledge base recall between the agent preview and your business integration are differences in document status, permissions, user/tenant context, and API parameters. Dify filters out documents that are disabled, not fully indexed, or archived, and also enforces strict permission checks at both the dataset and document level. If the integration context (API token, user role, or tenant) differs from the preview, or if the document's status isn't "enabled" and "indexing completed," some items (like your missing Project 3) won't be recalled in the integrated environment—even if they appear in the preview. Recent changes also mean that search and recall now depend on live API data and parameters like page, limit, and keyword, which can further affect results if not matched between environments [[source]](https://github.com/langgenius/dify/blob/aa71f88e1babd867524084ad361546e7e1e178b7/api/services/dataset_service.py) [[source]](https://github.com/langgenius/dify/pull/23538). To troubleshoot: check that Project 3 is enabled, not archived, and fully indexed; verify that the integration uses the same user/tenant context and permissions as the preview; and compare the API requests and parameters (including pagination and filters) used in both environments. If the issue persists, try querying the document list via the API directly to confirm its visibility and status. <!-- 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/79ba2681-5239-4c54-ae07-0ed91393671a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/79ba2681-5239-4c54-ae07-0ed91393671a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/79ba2681-5239-4c54-ae07-0ed91393671a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/79ba2681-5239-4c54-ae07-0ed91393671a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/79ba2681-5239-4c54-ae07-0ed91393671a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/79ba2681-5239-4c54-ae07-0ed91393671a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/79ba2681-5239-4c54-ae07-0ed91393671a?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/24519)
yindo commented 2026-02-21 19:26:05 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 25, 2025):

Please upgrade to latest version to see if this persists. The version is oudated.

@crazywoola commented on GitHub (Aug 25, 2025): Please upgrade to latest version to see if this persists. The version is oudated.
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 outdated 🐞 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#16432
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?