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

The message ‘Import successful’ appears during batch addition, but the imported data cannot be shown. #20910

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

Originally created by @KamenC on GitHub (Dec 9, 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.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I'm using a custom text chunking method to complete text chunking and then save it as a csv file in the batch add format. However, when importing this file into Dify v1.9.1, although it displays ‘Import completed’, the newly added data does not appear within the chunks. It is known that the same file imported successfully and shown correctly in version 1.7.1.

✔️ Expected Behavior

When batch-adding, the message ‘Import completed’ is shown, and the imported data is displayed correctly. Such as in version 1.7.1:
Image

❌ Actual Behavior

Although it displays ‘Import completed’, the newly added data does not appear within the chunks in version 1.9.1.
Image

Originally created by @KamenC on GitHub (Dec 9, 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.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I'm using a custom text chunking method to complete text chunking and then save it as a csv file in the batch add format. However, when importing this file into Dify v1.9.1, although it displays ‘Import completed’, the newly added data does not appear within the chunks. It is known that the same file imported successfully and shown correctly in version 1.7.1. ### ✔️ Expected Behavior When batch-adding, the message ‘Import completed’ is shown, and the imported data is displayed correctly. Such as in version 1.7.1: <img width="1386" height="872" alt="Image" src="https://github.com/user-attachments/assets/f2b84d3d-885e-4ebb-8b8d-8b4b182b22c2" /> ### ❌ Actual Behavior Although it displays ‘Import completed’, the newly added data does not appear within the chunks in version 1.9.1. <img width="1556" height="738" alt="Image" src="https://github.com/user-attachments/assets/b9abcdac-c505-488e-bf90-1cdaaa943cfa" />
yindo added the 🐞 bug label 2026-02-21 20:09:45 -05:00
yindo closed this issue 2026-02-21 20:09:45 -05:00
yindo commented 2026-02-21 20:09:45 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 9, 2025):

The most likely cause is a mismatch between your CSV format and what Dify v1.9.1 expects for batch import. The backend now strictly checks the CSV schema based on the document's chunking mode (QA vs. text). For QA mode, the CSV must have two columns (e.g., "question,answer"); for text mode, it must have one column (e.g., "segment content"). If your CSV doesn't match, the import can appear successful but no data will show in the UI. You can find the expected templates in the batch import modal or in the codebase for reference.

Other possible causes include stricter frontend validation of API URLs in Docker setups (avoid using localhost or 127.0.0.1 as your API base URL), or backend configuration issues like missing vector DB containers, Python dependencies, or embedding provider API keys, which can silently block chunk creation even if the import says "completed" citation 1 citation 2.

To troubleshoot:

  • Double-check your CSV matches the template for your document type.
  • Check Dify logs (API, worker, and frontend) for errors during import.
  • Make sure all backend services (vector DB, embedding provider, Python environment, locale) are running and configured.
  • Try importing a minimal CSV using the provided template to see if it appears.
  • If you have DB access, check if new segments are created after import.

If the problem persists, collect any error logs or warnings from the import process for further debugging.

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 (Dec 9, 2025): <!-- Answer --> The most likely cause is a mismatch between your CSV format and what Dify v1.9.1 expects for batch import. The backend now strictly checks the CSV schema based on the document's chunking mode (QA vs. text). For QA mode, the CSV must have two columns (e.g., "question,answer"); for text mode, it must have one column (e.g., "segment content"). If your CSV doesn't match, the import can appear successful but no data will show in the UI. You can find the expected templates in the batch import modal or in the codebase for reference. Other possible causes include stricter frontend validation of API URLs in Docker setups (avoid using localhost or 127.0.0.1 as your API base URL), or backend configuration issues like missing vector DB containers, Python dependencies, or embedding provider API keys, which can silently block chunk creation even if the import says "completed" [citation 1](https://github.com/langgenius/dify-docs/issues/543) [citation 2](https://github.com/langgenius/dify-docs/issues/397). To troubleshoot: - Double-check your CSV matches the template for your document type. - Check Dify logs (API, worker, and frontend) for errors during import. - Make sure all backend services (vector DB, embedding provider, Python environment, locale) are running and configured. - Try importing a minimal CSV using the provided template to see if it appears. - If you have DB access, check if new segments are created after import. If the problem persists, collect any error logs or warnings from the import process for further debugging. <!-- 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/732b489c-ed42-4d20-adb1-9238855961bc?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/732b489c-ed42-4d20-adb1-9238855961bc?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/732b489c-ed42-4d20-adb1-9238855961bc?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/732b489c-ed42-4d20-adb1-9238855961bc?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/732b489c-ed42-4d20-adb1-9238855961bc?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/732b489c-ed42-4d20-adb1-9238855961bc?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/732b489c-ed42-4d20-adb1-9238855961bc?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=The%20most%20likely%20cause%20is%20a%20mismatch%20between%20your%20CSV%20format%20and%20what%20Dify%20v1.9.1%20expects%20for%20batch%20import.%20The%20backend%20now%20strictly%20checks%20the%20CSV%20schema%20based%20on%20the%20document%27s%20chunking%20mode%20%28QA%20vs.%20text%29.%20For%20QA%20mode%2C%20the%20CSV%20must%20have%20two%20columns%20%28e.g.%2C%20%22question%2Canswer%22%29%3B%20for%20text%20mode%2C%20it%20must%20have%20one%20column%20%28e.g.%2C%20%22segment%20content%22%29.%20If%20your%20CSV%20doesn%27t%20match%2C%20the%20import%20can%20appear%20successful%20but%20no%20data%20will%20show%20in%20the%20UI.%20You%20can%20find%20the%20expected%20templates%20in%20the%20batch%20import%20modal%20or%20in%20the%20codebase%20for%20reference.%0A%0AOther%20possible%20causes%20include%20stricter%20frontend%20validation%20of%20API%20URLs%20in%20Docker%20setups%20%28avoid%20using%20localhost%20or%20127.0.0.1%20as%20your%20API%20base%20URL%29%2C%20or%20backend%20configuration%20issues%20like%20missing%20vector%20DB%20containers%2C%20Python%20dependencies%2C%20or%20embedding%20provider%20API%20keys%2C%20which%20can%20silently%20block%20chunk%20creation%20even%20if%20the%20import%20says%20%22completed%22%C2%A0%5Bcitation%201%5D%28https%3A//github.com/langgenius/dify-docs/issues/543%29%C2%A0%5Bcitation%202%5D%28https%3A//github.com/langgenius/dify-docs/issues/397%29.%0A%0ATo%20troubleshoot%3A%0A-%20Double-check%20your%20CSV%20matches%20the%20template%20for%20your%20document%20type.%0A-%20Check%20Dify%20logs%20%28API%2C%20worker%2C%20and%20frontend%29%20for%20errors%20during%20import.%0A-%20Make%20sure%20all%20backend%20services%20%28vector%20DB%2C%20embedding%20provider%2C%20Python%20environment%2C%20locale%29%20are%20running%20and%20configured.%0A-%20Try%20importing%20a%20minimal%20CSV%20using%20the%20provided%20template%20to%20see%20if%20it%20appears.%0A-%20If%20you%20have%20DB%20access%2C%20check%20if%20new%20segments%20are%20created%20after%20import.%0A%0AIf%20the%20problem%20persists%2C%20collect%20any%20error%20logs%20or%20warnings%20from%20the%20import%20process%20for%20further%20debugging.)&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/29378)
yindo commented 2026-02-21 20:09:46 -05:00
Author
Owner
Copy Link
Copy Source

@KamenC commented on GitHub (Dec 9, 2025):

The most likely cause is a mismatch between your CSV format and what Dify v1.9.1 expects for batch import. The backend now strictly checks the CSV schema based on the document's chunking mode (QA vs. text). For QA mode, the CSV must have two columns (e.g., "question,answer"); for text mode, it must have one column (e.g., "segment content"). If your CSV doesn't match, the import can appear successful but no data will show in the UI. You can find the expected templates in the batch import modal or in the codebase for reference.最可能的原因是你的 CSV 格式与 Dify v1.9.1 对批次导入的预期不匹配。后端现在严格根据文档的分块模式（QA 与文本）来严格检查 CSV 模式。对于 QA 模式，CSV 必须有两列（例如“问，答”）;对于文本模式，必须只有一列（例如，“段内容”）。如果你的 CSV 不匹配，导入看起来可能成功，但界面上不会显示任何数据。你可以在批量导入模态或代码库中找到预期模板供参考。

Other possible causes include stricter frontend validation of API URLs in Docker setups (avoid using localhost or 127.0.0.1 as your API base URL), or backend configuration issues like missing vector DB containers, Python dependencies, or embedding provider API keys, which can silently block chunk creation even if the import says "completed" citation 1 citation 2.其他可能的原因包括 Docker 设置中对 API URL 的前端验证更严格（避免使用 localhost 或 127.0.0.1 作为 API 基础 URL），或者后端配置问题，比如缺少矢量数据库容器、Python 依赖，或者嵌入 API 提供者密钥，即使导入显示“已完成”，引用 1  引用 2，也会无声阻碍块的创建。

To troubleshoot:  排查方法：

  • Double-check your CSV matches the template for your document type.请仔细核对你的 CSV 是否符合你文档类型的模板。
  • Check Dify logs (API, worker, and frontend) for errors during import.检查 Dify 日志（API、工作端和前端）导入时是否有错误。
  • Make sure all backend services (vector DB, embedding provider, Python environment, locale) are running and configured.确保所有后端服务（矢量数据库、嵌入提供商、Python 环境、本地环境）都在运行和配置。
  • Try importing a minimal CSV using the provided template to see if it appears.试着用提供的模板导入一个最小 CSV，看看是否会出现。
  • If you have DB access, check if new segments are created after import.如果你有数据库访问权限，检查导入后是否创建了新的分段。

If the problem persists, collect any error logs or warnings from the import process for further debugging.如果问题依旧，收集导入过程中的任何错误日志或警告以便进一步调试。

To reply, just mention @dosu.回复时，只需提及 @dosu。

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other我表现得怎么样？很好 |无关紧要 |错误 |冗长 |幻觉 |报告 🐛 |其他

Chat with Dosu Open in Cursor Join Discord Share on X

I have attempted to use the template file ‘template.csv’ provided by the official Dify platform for batch additions, yet the issue I described persists. Therefore, it is not a matter of my CSV file format being incompatible. The identical ‘template.csv’ file can be imported and displayed correctly in version 1.7.1.

@KamenC commented on GitHub (Dec 9, 2025): > The most likely cause is a mismatch between your CSV format and what Dify v1.9.1 expects for batch import. The backend now strictly checks the CSV schema based on the document's chunking mode (QA vs. text). For QA mode, the CSV must have two columns (e.g., "question,answer"); for text mode, it must have one column (e.g., "segment content"). If your CSV doesn't match, the import can appear successful but no data will show in the UI. You can find the expected templates in the batch import modal or in the codebase for reference.最可能的原因是你的 CSV 格式与 Dify v1.9.1 对批次导入的预期不匹配。后端现在严格根据文档的分块模式（QA 与文本）来严格检查 CSV 模式。对于 QA 模式，CSV 必须有两列（例如“问，答”）;对于文本模式，必须只有一列（例如，“段内容”）。如果你的 CSV 不匹配，导入看起来可能成功，但界面上不会显示任何数据。你可以在批量导入模态或代码库中找到预期模板供参考。 > > Other possible causes include stricter frontend validation of API URLs in Docker setups (avoid using localhost or 127.0.0.1 as your API base URL), or backend configuration issues like missing vector DB containers, Python dependencies, or embedding provider API keys, which can silently block chunk creation even if the import says "completed" [citation 1](https://github.com/langgenius/dify-docs/issues/543) [citation 2](https://github.com/langgenius/dify-docs/issues/397).其他可能的原因包括 Docker 设置中对 API URL 的前端验证更严格（避免使用 localhost 或 127.0.0.1 作为 API 基础 URL），或者后端配置问题，比如缺少矢量数据库容器、Python 依赖，或者嵌入 API 提供者密钥，即使导入显示“已完成”，引用 [1](https://github.com/langgenius/dify-docs/issues/543) [ 引用 2](https://github.com/langgenius/dify-docs/issues/397)，也会无声阻碍块的创建。 > > To troubleshoot:  排查方法： > > * Double-check your CSV matches the template for your document type.请仔细核对你的 CSV 是否符合你文档类型的模板。 > * Check Dify logs (API, worker, and frontend) for errors during import.检查 Dify 日志（API、工作端和前端）导入时是否有错误。 > * Make sure all backend services (vector DB, embedding provider, Python environment, locale) are running and configured.确保所有后端服务（矢量数据库、嵌入提供商、Python 环境、本地环境）都在运行和配置。 > * Try importing a minimal CSV using the provided template to see if it appears.试着用提供的模板导入一个最小 CSV，看看是否会出现。 > * If you have DB access, check if new segments are created after import.如果你有数据库访问权限，检查导入后是否创建了新的分段。 > > If the problem persists, collect any error logs or warnings from the import process for further debugging.如果问题依旧，收集导入过程中的任何错误日志或警告以便进一步调试。 > > _To reply, just mention [@dosu](https://go.dosu.dev/dosubot).回复时，只需提及 [@dosu](https://go.dosu.dev/dosubot)。_ > > How did I do? [Good](https://app.dosu.dev/response-feedback/732b489c-ed42-4d20-adb1-9238855961bc?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/732b489c-ed42-4d20-adb1-9238855961bc?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/732b489c-ed42-4d20-adb1-9238855961bc?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/732b489c-ed42-4d20-adb1-9238855961bc?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/732b489c-ed42-4d20-adb1-9238855961bc?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/732b489c-ed42-4d20-adb1-9238855961bc?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/732b489c-ed42-4d20-adb1-9238855961bc?feedback_type=other)我表现得怎么样？很好 |无关紧要 |错误 |冗长 |幻觉 |报告 🐛 |其他 > > [<img alt="Chat with Dosu" width="61" height="20" src="https://camo.githubusercontent.com/7c571478962a6b8a5d47cac74b6824c75e4f6731bba52377e6007f9150462923/68747470733a2f2f646f73752e6465762f646f73752d636861742d62616467652e737667">](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [<img alt="Open in Cursor" width="120" height="20" src="https://camo.githubusercontent.com/bdf7dbded65ee585887f47e5fd6fa099ea0933088b4b03d02e83b4def50154d4/68747470733a2f2f646f73752e6465762f646f73752d696e2d637572736f722e737667">](https://cursor.com/link/prompt?text=The%20most%20likely%20cause%20is%20a%20mismatch%20between%20your%20CSV%20format%20and%20what%20Dify%20v1.9.1%20expects%20for%20batch%20import.%20The%20backend%20now%20strictly%20checks%20the%20CSV%20schema%20based%20on%20the%20document%27s%20chunking%20mode%20%28QA%20vs.%20text%29.%20For%20QA%20mode%2C%20the%20CSV%20must%20have%20two%20columns%20%28e.g.%2C%20%22question%2Canswer%22%29%3B%20for%20text%20mode%2C%20it%20must%20have%20one%20column%20%28e.g.%2C%20%22segment%20content%22%29.%20If%20your%20CSV%20doesn%27t%20match%2C%20the%20import%20can%20appear%20successful%20but%20no%20data%20will%20show%20in%20the%20UI.%20You%20can%20find%20the%20expected%20templates%20in%20the%20batch%20import%20modal%20or%20in%20the%20codebase%20for%20reference.%0A%0AOther%20possible%20causes%20include%20stricter%20frontend%20validation%20of%20API%20URLs%20in%20Docker%20setups%20%28avoid%20using%20localhost%20or%20127.0.0.1%20as%20your%20API%20base%20URL%29%2C%20or%20backend%20configuration%20issues%20like%20missing%20vector%20DB%20containers%2C%20Python%20dependencies%2C%20or%20embedding%20provider%20API%20keys%2C%20which%20can%20silently%20block%20chunk%20creation%20even%20if%20the%20import%20says%20%22completed%22%C2%A0%5Bcitation%201%5D%28https%3A//github.com/langgenius/dify-docs/issues/543%29%C2%A0%5Bcitation%202%5D%28https%3A//github.com/langgenius/dify-docs/issues/397%29.%0A%0ATo%20troubleshoot%3A%0A-%20Double-check%20your%20CSV%20matches%20the%20template%20for%20your%20document%20type.%0A-%20Check%20Dify%20logs%20%28API%2C%20worker%2C%20and%20frontend%29%20for%20errors%20during%20import.%0A-%20Make%20sure%20all%20backend%20services%20%28vector%20DB%2C%20embedding%20provider%2C%20Python%20environment%2C%20locale%29%20are%20running%20and%20configured.%0A-%20Try%20importing%20a%20minimal%20CSV%20using%20the%20provided%20template%20to%20see%20if%20it%20appears.%0A-%20If%20you%20have%20DB%20access%2C%20check%20if%20new%20segments%20are%20created%20after%20import.%0A%0AIf%20the%20problem%20persists%2C%20collect%20any%20error%20logs%20or%20warnings%20from%20the%20import%20process%20for%20further%20debugging.) [<img alt="Join Discord" width="49" height="20" src="https://camo.githubusercontent.com/7d2066700925db1e370d956834f9ea0e5bc92cecbe84963fbd2a363e45091b4e/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6a6f696e2d3538363546323f6c6f676f3d646973636f7264266c6f676f436f6c6f723d7768697465266c6162656c3d">](https://go.dosu.dev/discord-bot) [<img alt="Share on X" width="58" height="20" src="https://camo.githubusercontent.com/a8bd7f3fcf3f5e3bd124eee9ae50ae2ac17b40971726665ac2121d48f9aee155/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f582d73686172652d626c61636b">](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/29378) I have attempted to use the template file ‘template.csv’ provided by the official Dify platform for batch additions, yet the issue I described persists. Therefore, it is not a matter of my CSV file format being incompatible. The identical ‘template.csv’ file can be imported and displayed correctly in version 1.7.1.
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#20910
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?