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

When DB_TYPE = mysql and VECTOR_STORE = weaviate, the knowledge base displays the error "Dataset not found". #20819

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

Originally created by @XIN-github-bash on GitHub (Dec 5, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Dify version
1.10.1

Cloud or Self Hosted
Self Hosted (Docker)

Steps to reproduce
Set DB_TYPE to mysql, VECTOR_STORE to weakate, create a knowledge base, and then open the knowledge base to view details.

✔️ Expected Behavior
Displaying a list of knowledge base chunks

❌ Actual Behavior

Image

Report this error "Dataset not found. You have requested this URI [/console/api/datasets/98ee35b9-0ca1-4017-9180-f8a85abd9a1e/documents] but did you mean /console/api/datasets/uuid:dataset_id/documents?"

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @XIN-github-bash on GitHub (Dec 5, 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] 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] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. **Dify version** 1.10.1 **Cloud or Self Hosted** Self Hosted (Docker) **Steps to reproduce** Set DB_TYPE to mysql, VECTOR_STORE to weakate, create a knowledge base, and then open the knowledge base to view details. **✔️ Expected Behavior** Displaying a list of knowledge base chunks **❌ Actual Behavior** <img width="1920" height="968" alt="Image" src="https://github.com/user-attachments/assets/308afb37-f292-4fcb-9544-3dd6d5ef9c74" /> Report this error "Dataset not found. You have requested this URI [/console/api/datasets/98ee35b9-0ca1-4017-9180-f8a85abd9a1e/documents] but did you mean /console/api/datasets/<uuid:dataset_id>/documents?" ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 🐞 bug label 2026-02-21 20:09:08 -05:00
yindo closed this issue 2026-02-21 20:09:08 -05:00
yindo commented 2026-02-21 20:09:08 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi @XIN-github-bash! I'm Dosu and I’m helping the dify team.

This "Dataset not found" error with MySQL and Weaviate in Dify v1.10.1 is a known issue, often caused by one or more of the following:

  • UUID format mismatch: MySQL stores UUIDs as 36-character strings with dashes, but some queries may use 32-character hex strings without dashes, leading to empty results and this error. Workarounds include patching the StringUUID type to ensure consistent UUID formatting, or making sure all UUIDs in queries and the database use the same (hyphenated) format. Permanent fixes for this have been merged after v1.10.1, so upgrading is recommended if possible (details).
  • Weaviate container not running: In self-hosted Docker setups, Dify does not start the Weaviate vector database by default. You need to start it manually with the correct Docker Compose profile and environment variables. If the Weaviate container isn't running, you'll get "Dataset not found" errors (details) (more context).
  • Configuration/environment issues: Make sure DB_TYPE, VECTOR_STORE, and COMPOSE_PROFILES are all set correctly in your environment files. For example, add this to your middleware.env: 
    COMPOSE_PROFILES=${VECTOR_STORE:-weaviate},${DB_TYPE:-mysql}
    This ensures Docker Compose starts both the MySQL and Weaviate containers (details).

Troubleshooting steps:

  1. Check that the dataset ID in the API URI matches the format stored in your MySQL database (should be a 36-character UUID with dashes).
  2. Make sure the Weaviate container is running and healthy: 
    docker compose --profile weaviate up -d
  3. Verify your .env and middleware.env files include the correct DB_TYPE, VECTOR_STORE, and COMPOSE_PROFILES settings.
  4. If you can't upgrade Dify, consider patching the UUID handling in your codebase as described above.
  5. Double-check that the dataset actually exists in your database and hasn't been deleted or corrupted.

If you follow these steps and still see the error, upgrading to a newer Dify version with improved MySQL and UUID handling is strongly recommended.

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 5, 2025): <!-- Greeting --> Hi @XIN-github-bash! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This "Dataset not found" error with MySQL and Weaviate in Dify v1.10.1 is a known issue, often caused by one or more of the following: - **UUID format mismatch**: MySQL stores UUIDs as 36-character strings with dashes, but some queries may use 32-character hex strings without dashes, leading to empty results and this error. Workarounds include patching the `StringUUID` type to ensure consistent UUID formatting, or making sure all UUIDs in queries and the database use the same (hyphenated) format. Permanent fixes for this have been merged after v1.10.1, so upgrading is recommended if possible [(details)](https://github.com/langgenius/dify/issues/28942). - **Weaviate container not running**: In self-hosted Docker setups, Dify does not start the Weaviate vector database by default. You need to start it manually with the correct Docker Compose profile and environment variables. If the Weaviate container isn't running, you'll get "Dataset not found" errors [(details)](https://github.com/langgenius/dify/issues/25832) [(more context)](https://github.com/langgenius/dify/issues/29135). - **Configuration/environment issues**: Make sure `DB_TYPE`, `VECTOR_STORE`, and `COMPOSE_PROFILES` are all set correctly in your environment files. For example, add this to your `middleware.env`: ``` COMPOSE_PROFILES=${VECTOR_STORE:-weaviate},${DB_TYPE:-mysql} ``` This ensures Docker Compose starts both the MySQL and Weaviate containers [(details)](https://github.com/langgenius/dify/issues/28540). **Troubleshooting steps:** 1. Check that the dataset ID in the API URI matches the format stored in your MySQL database (should be a 36-character UUID with dashes). 2. Make sure the Weaviate container is running and healthy: ``` docker compose --profile weaviate up -d ``` 3. Verify your `.env` and `middleware.env` files include the correct `DB_TYPE`, `VECTOR_STORE`, and `COMPOSE_PROFILES` settings. 4. If you can't upgrade Dify, consider patching the UUID handling in your codebase as described above. 5. Double-check that the dataset actually exists in your database and hasn't been deleted or corrupted. If you follow these steps and still see the error, upgrading to a newer Dify version with improved MySQL and UUID handling is strongly recommended. <!-- 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/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?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%20%22Dataset%20not%20found%22%20error%20with%20MySQL%20and%20Weaviate%20in%20Dify%20v1.10.1%20is%20a%20known%20issue%2C%20often%20caused%20by%20one%20or%20more%20of%20the%20following%3A%0A%0A-%20%2A%2AUUID%20format%20mismatch%2A%2A%3A%20MySQL%20stores%20UUIDs%20as%2036-character%20strings%20with%20dashes%2C%20but%20some%20queries%20may%20use%2032-character%20hex%20strings%20without%20dashes%2C%20leading%20to%20empty%20results%20and%20this%20error.%20Workarounds%20include%20patching%20the%20%60StringUUID%60%20type%20to%20ensure%20consistent%20UUID%20formatting%2C%20or%20making%20sure%20all%20UUIDs%20in%20queries%20and%20the%20database%20use%20the%20same%20%28hyphenated%29%20format.%20Permanent%20fixes%20for%20this%20have%20been%20merged%20after%20v1.10.1%2C%20so%20upgrading%20is%20recommended%20if%20possible%20%5B%28details%29%5D%28https%3A//github.com/langgenius/dify/issues/28942%29.%0A-%20%2A%2AWeaviate%20container%20not%20running%2A%2A%3A%20In%20self-hosted%20Docker%20setups%2C%20Dify%20does%20not%20start%20the%20Weaviate%20vector%20database%20by%20default.%20You%20need%20to%20start%20it%20manually%20with%20the%20correct%20Docker%20Compose%20profile%20and%20environment%20variables.%20If%20the%20Weaviate%20container%20isn%27t%20running%2C%20you%27ll%20get%20%22Dataset%20not%20found%22%20errors%20%5B%28details%29%5D%28https%3A//github.com/langgenius/dify/issues/25832%29%20%5B%28more%20context%29%5D%28https%3A//github.com/langgenius/dify/issues/29135%29.%0A-%20%2A%2AConfiguration/environment%20issues%2A%2A%3A%20Make%20sure%20%60DB_TYPE%60%2C%20%60VECTOR_STORE%60%2C%20and%20%60COMPOSE_PROFILES%60%20are%20all%20set%20correctly%20in%20your%20environment%20files.%20For%20example%2C%20add%20this%20to%20your%20%60middleware.env%60%3A%0A%20%20%60%60%60%0A%20%20COMPOSE_PROFILES%3D%24%7BVECTOR_STORE%3A-weaviate%7D%2C%24%7BDB_TYPE%3A-mysql%7D%0A%20%20%60%60%60%0A%20%20This%20ensures%20Docker%20Compose%20starts%20both%20the%20MySQL%20and%20Weaviate%20containers%20%5B%28details%29%5D%28https%3A//github.com/langgenius/dify/issues/28540%29.%0A%0A%2A%2ATroubleshooting%20steps%3A%2A%2A%0A1.%20Check%20that%20the%20dataset%20ID%20in%20the%20API%20URI%20matches%20the%20format%20stored%20in%20your%20MySQL%20database%20%28should%20be%20a%2036-character%20UUID%20with%20dashes%29.%0A2.%20Make%20sure%20the%20Weaviate%20container%20is%20running%20and%20healthy%3A%20%20%0A%20%20%20%60%60%60%0A%20%20%20docker%20compose%20--profile%20weaviate%20up%20-d%0A%20%20%20%60%60%60%0A3.%20Verify%20your%20%60.env%60%20and%20%60middleware.env%60%20files%20include%20the%20correct%20%60DB_TYPE%60%2C%20%60VECTOR_STORE%60%2C%20and%20%60COMPOSE_PROFILES%60%20settings.%0A4.%20If%20you%20can%27t%20upgrade%20Dify%2C%20consider%20patching%20the%20UUID%20handling%20in%20your%20codebase%20as%20described%20above.%0A5.%20Double-check%20that%20the%20dataset%20actually%20exists%20in%20your%20database%20and%20hasn%27t%20been%20deleted%20or%20corrupted.%0A%0AIf%20you%20follow%20these%20steps%20and%20still%20see%20the%20error%2C%20upgrading%20to%20a%20newer%20Dify%20version%20with%20improved%20MySQL%20and%20UUID%20handling%20is%20strongly%20recommended.)&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/29181)
yindo commented 2026-02-21 20:09:08 -05:00
Author
Owner
Copy Link
Copy Source

@XIN-github-bash commented on GitHub (Dec 5, 2025):

Hi @XIN-github-bash! I'm Dosu and I’m helping the dify team.

This "Dataset not found" error with MySQL and Weaviate in Dify v1.10.1 is a known issue, often caused by one or more of the following:

  • UUID format mismatch: MySQL stores UUIDs as 36-character strings with dashes, but some queries may use 32-character hex strings without dashes, leading to empty results and this error. Workarounds include patching the StringUUID type to ensure consistent UUID formatting, or making sure all UUIDs in queries and the database use the same (hyphenated) format. Permanent fixes for this have been merged after v1.10.1, so upgrading is recommended if possible (details).

  • Weaviate container not running: In self-hosted Docker setups, Dify does not start the Weaviate vector database by default. You need to start it manually with the correct Docker Compose profile and environment variables. If the Weaviate container isn't running, you'll get "Dataset not found" errors (details) (more context).

  • Configuration/environment issues: Make sure DB_TYPE, VECTOR_STORE, and COMPOSE_PROFILES are all set correctly in your environment files. For example, add this to your middleware.env:

    COMPOSE_PROFILES=${VECTOR_STORE:-weaviate},${DB_TYPE:-mysql}

    This ensures Docker Compose starts both the MySQL and Weaviate containers (details).

Troubleshooting steps:

  1. Check that the dataset ID in the API URI matches the format stored in your MySQL database (should be a 36-character UUID with dashes).
  2. Make sure the Weaviate container is running and healthy: 
    docker compose --profile weaviate up -d
  3. Verify your .env and middleware.env files include the correct DB_TYPE, VECTOR_STORE, and COMPOSE_PROFILES settings.
  4. If you can't upgrade Dify, consider patching the UUID handling in your codebase as described above.
  5. Double-check that the dataset actually exists in your database and hasn't been deleted or corrupted.

If you follow these steps and still see the error, upgrading to a newer Dify version with improved MySQL and UUID handling is strongly recommended.

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

My configuration is as follows:
COMPOSE_PROFILES=${VECTOR_STORE:-weaviate},${DB_TYPE:-mysql}
DB_TYPE=mysql
VECTOR_STORE=weaviate

And my Docker containers are as follows:

Image weaviate is started

I also compared the class_prefix of the index_struct in the mysql datasets table with the data from weaviate, which are shown in the following two JSON files:
mysql index_struct：

{"type": "weaviate", "vector_store": {"class_prefix": "Vector_index_98ee35b9_0ca1_4017_9180_f8a85abd9a1e_Node"}}

weaviate schema:

{"classes":[{"class":"Vector_index_98ee35b9_0ca1_4017_9180_f8a85abd9a1e_Node","invertedIndexConfig":{"bm25":{"b":0.75,"k1":1.2},"cleanupIntervalSeconds":60,"stopwords":{"additions":null,"preset":"en","removals":null}},"multiTenancyConfig":{"autoTenantActivation":false,"autoTenantCreation":false,"enabled":false},"properties":[{"dataType":["text"],"indexFilterable":true,"indexRangeFilters":false,"indexSearchable":true,"name":"text","tokenization":"word"},{"dataType":["text"],"indexFilterable":true,"indexRangeFilters":false,"indexSearchable":true,"name":"document_id","tokenization":"word"},{"dataType":["text"],"indexFilterable":true,"indexRangeFilters":false,"indexSearchable":true,"name":"doc_id","tokenization":"word"},{"dataType":["int"],"indexFilterable":true,"indexRangeFilters":false,"indexSearchable":false,"name":"chunk_index"},{"dataType":["text"],"description":"This property was generated by Weaviate's auto-schema feature on Fri Dec  5 05:57:20 2025","indexFilterable":true,"indexRangeFilters":false,"indexSearchable":true,"name":"doc_hash","tokenization":"word"},{"dataType":["uuid"],"description":"This property was generated by Weaviate's auto-schema feature on Fri Dec  5 05:57:20 2025","indexFilterable":true,"indexRangeFilters":false,"indexSearchable":false,"name":"dataset_id"},{"dataType":["text"],"description":"This property was generated by Weaviate's auto-schema feature on Fri Dec  5 05:57:24 2025","indexFilterable":true,"indexRangeFilters":false,"indexSearchable":true,"name":"source","tokenization":"word"}],"replicationConfig":{"asyncEnabled":false,"deletionStrategy":"DeleteOnConflict","factor":1},"shardingConfig":{"actualCount":1,"actualVirtualCount":128,"desiredCount":1,"desiredVirtualCount":128,"function":"murmur3","key":"_id","strategy":"hash","virtualPerPhysical":128},"vectorConfig":{"default":{"vectorIndexConfig":{"bq":{"enabled":false},"cleanupIntervalSeconds":300,"distance":"cosine","dynamicEfFactor":8,"dynamicEfMax":500,"dynamicEfMin":100,"ef":-1,"efConstruction":128,"filterStrategy":"sweeping","flatSearchCutoff":40000,"maxConnections":32,"pq":{"bitCompression":false,"centroids":256,"enabled":false,"encoder":{"distribution":"log-normal","type":"kmeans"},"segments":0,"trainingLimit":100000},"skip":false,"sq":{"enabled":false,"rescoreLimit":20,"trainingLimit":100000},"vectorCacheMaxObjects":1000000000000},"vectorIndexType":"hnsw","vectorizer":{"none":{}}}}}]}

I also have the latest version of the StringUUID method.

Image

But it still reports "Dataset not found. You have requested this URI [/console/api/datasets/98ee35b9-0ca1-4017-9180-f8a85abd9a1e/documents] but did you mean /console/api/datasets/uuid:dataset_id/documents?"

@XIN-github-bash commented on GitHub (Dec 5, 2025): > Hi [@XIN-github-bash](https://github.com/XIN-github-bash)! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. > > This "Dataset not found" error with MySQL and Weaviate in Dify v1.10.1 is a known issue, often caused by one or more of the following: > > * **UUID format mismatch**: MySQL stores UUIDs as 36-character strings with dashes, but some queries may use 32-character hex strings without dashes, leading to empty results and this error. Workarounds include patching the `StringUUID` type to ensure consistent UUID formatting, or making sure all UUIDs in queries and the database use the same (hyphenated) format. Permanent fixes for this have been merged after v1.10.1, so upgrading is recommended if possible [(details)](https://github.com/langgenius/dify/issues/28942). > * **Weaviate container not running**: In self-hosted Docker setups, Dify does not start the Weaviate vector database by default. You need to start it manually with the correct Docker Compose profile and environment variables. If the Weaviate container isn't running, you'll get "Dataset not found" errors [(details)](https://github.com/langgenius/dify/issues/25832) [(more context)](https://github.com/langgenius/dify/issues/29135). > * **Configuration/environment issues**: Make sure `DB_TYPE`, `VECTOR_STORE`, and `COMPOSE_PROFILES` are all set correctly in your environment files. For example, add this to your `middleware.env`: > ``` > COMPOSE_PROFILES=${VECTOR_STORE:-weaviate},${DB_TYPE:-mysql} > ``` > > > > > This ensures Docker Compose starts both the MySQL and Weaviate containers [(details)](https://github.com/langgenius/dify/issues/28540). > > **Troubleshooting steps:** > > 1. Check that the dataset ID in the API URI matches the format stored in your MySQL database (should be a 36-character UUID with dashes). > 2. Make sure the Weaviate container is running and healthy: > ``` > docker compose --profile weaviate up -d > ``` > 3. Verify your `.env` and `middleware.env` files include the correct `DB_TYPE`, `VECTOR_STORE`, and `COMPOSE_PROFILES` settings. > 4. If you can't upgrade Dify, consider patching the UUID handling in your codebase as described above. > 5. Double-check that the dataset actually exists in your database and hasn't been deleted or corrupted. > > If you follow these steps and still see the error, upgrading to a newer Dify version with improved MySQL and UUID handling is strongly recommended. > > _To reply, just mention [@dosu](https://go.dosu.dev/dosubot)._ > > How did I do? [Good](https://app.dosu.dev/response-feedback/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ed99b0af-1c42-4d9f-ad2c-d1b9c242d9d8?feedback_type=other) > > [![Chat with Dosu](https://camo.githubusercontent.com/7c571478962a6b8a5d47cac74b6824c75e4f6731bba52377e6007f9150462923/68747470733a2f2f646f73752e6465762f646f73752d636861742d62616467652e737667)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Open in Cursor](https://camo.githubusercontent.com/bdf7dbded65ee585887f47e5fd6fa099ea0933088b4b03d02e83b4def50154d4/68747470733a2f2f646f73752e6465762f646f73752d696e2d637572736f722e737667)](https://cursor.com/link/prompt?text=This%20%22Dataset%20not%20found%22%20error%20with%20MySQL%20and%20Weaviate%20in%20Dify%20v1.10.1%20is%20a%20known%20issue%2C%20often%20caused%20by%20one%20or%20more%20of%20the%20following%3A%0A%0A-%20%2A%2AUUID%20format%20mismatch%2A%2A%3A%20MySQL%20stores%20UUIDs%20as%2036-character%20strings%20with%20dashes%2C%20but%20some%20queries%20may%20use%2032-character%20hex%20strings%20without%20dashes%2C%20leading%20to%20empty%20results%20and%20this%20error.%20Workarounds%20include%20patching%20the%20%60StringUUID%60%20type%20to%20ensure%20consistent%20UUID%20formatting%2C%20or%20making%20sure%20all%20UUIDs%20in%20queries%20and%20the%20database%20use%20the%20same%20%28hyphenated%29%20format.%20Permanent%20fixes%20for%20this%20have%20been%20merged%20after%20v1.10.1%2C%20so%20upgrading%20is%20recommended%20if%20possible%20%5B%28details%29%5D%28https%3A//github.com/langgenius/dify/issues/28942%29.%0A-%20%2A%2AWeaviate%20container%20not%20running%2A%2A%3A%20In%20self-hosted%20Docker%20setups%2C%20Dify%20does%20not%20start%20the%20Weaviate%20vector%20database%20by%20default.%20You%20need%20to%20start%20it%20manually%20with%20the%20correct%20Docker%20Compose%20profile%20and%20environment%20variables.%20If%20the%20Weaviate%20container%20isn%27t%20running%2C%20you%27ll%20get%20%22Dataset%20not%20found%22%20errors%20%5B%28details%29%5D%28https%3A//github.com/langgenius/dify/issues/25832%29%20%5B%28more%20context%29%5D%28https%3A//github.com/langgenius/dify/issues/29135%29.%0A-%20%2A%2AConfiguration/environment%20issues%2A%2A%3A%20Make%20sure%20%60DB_TYPE%60%2C%20%60VECTOR_STORE%60%2C%20and%20%60COMPOSE_PROFILES%60%20are%20all%20set%20correctly%20in%20your%20environment%20files.%20For%20example%2C%20add%20this%20to%20your%20%60middleware.env%60%3A%0A%20%20%60%60%60%0A%20%20COMPOSE_PROFILES%3D%24%7BVECTOR_STORE%3A-weaviate%7D%2C%24%7BDB_TYPE%3A-mysql%7D%0A%20%20%60%60%60%0A%20%20This%20ensures%20Docker%20Compose%20starts%20both%20the%20MySQL%20and%20Weaviate%20containers%20%5B%28details%29%5D%28https%3A//github.com/langgenius/dify/issues/28540%29.%0A%0A%2A%2ATroubleshooting%20steps%3A%2A%2A%0A1.%20Check%20that%20the%20dataset%20ID%20in%20the%20API%20URI%20matches%20the%20format%20stored%20in%20your%20MySQL%20database%20%28should%20be%20a%2036-character%20UUID%20with%20dashes%29.%0A2.%20Make%20sure%20the%20Weaviate%20container%20is%20running%20and%20healthy%3A%20%20%0A%20%20%20%60%60%60%0A%20%20%20docker%20compose%20--profile%20weaviate%20up%20-d%0A%20%20%20%60%60%60%0A3.%20Verify%20your%20%60.env%60%20and%20%60middleware.env%60%20files%20include%20the%20correct%20%60DB_TYPE%60%2C%20%60VECTOR_STORE%60%2C%20and%20%60COMPOSE_PROFILES%60%20settings.%0A4.%20If%20you%20can%27t%20upgrade%20Dify%2C%20consider%20patching%20the%20UUID%20handling%20in%20your%20codebase%20as%20described%20above.%0A5.%20Double-check%20that%20the%20dataset%20actually%20exists%20in%20your%20database%20and%20hasn%27t%20been%20deleted%20or%20corrupted.%0A%0AIf%20you%20follow%20these%20steps%20and%20still%20see%20the%20error%2C%20upgrading%20to%20a%20newer%20Dify%20version%20with%20improved%20MySQL%20and%20UUID%20handling%20is%20strongly%20recommended.) [![Join Discord](https://camo.githubusercontent.com/7d2066700925db1e370d956834f9ea0e5bc92cecbe84963fbd2a363e45091b4e/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6a6f696e2d3538363546323f6c6f676f3d646973636f7264266c6f676f436f6c6f723d7768697465266c6162656c3d)](https://go.dosu.dev/discord-bot) [![Share on X](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/29181) My configuration is as follows: `COMPOSE_PROFILES=${VECTOR_STORE:-weaviate},${DB_TYPE:-mysql}` `DB_TYPE=mysql` `VECTOR_STORE=weaviate` And my Docker containers are as follows: <img width="1418" height="242" alt="Image" src="https://github.com/user-attachments/assets/ddd044e0-0d10-445b-ab75-63964ed180d6" /> weaviate is started I also compared the class_prefix of the index_struct in the mysql datasets table with the data from weaviate, which are shown in the following two JSON files: mysql index_struct： ``` {"type": "weaviate", "vector_store": {"class_prefix": "Vector_index_98ee35b9_0ca1_4017_9180_f8a85abd9a1e_Node"}} ``` weaviate schema: ``` {"classes":[{"class":"Vector_index_98ee35b9_0ca1_4017_9180_f8a85abd9a1e_Node","invertedIndexConfig":{"bm25":{"b":0.75,"k1":1.2},"cleanupIntervalSeconds":60,"stopwords":{"additions":null,"preset":"en","removals":null}},"multiTenancyConfig":{"autoTenantActivation":false,"autoTenantCreation":false,"enabled":false},"properties":[{"dataType":["text"],"indexFilterable":true,"indexRangeFilters":false,"indexSearchable":true,"name":"text","tokenization":"word"},{"dataType":["text"],"indexFilterable":true,"indexRangeFilters":false,"indexSearchable":true,"name":"document_id","tokenization":"word"},{"dataType":["text"],"indexFilterable":true,"indexRangeFilters":false,"indexSearchable":true,"name":"doc_id","tokenization":"word"},{"dataType":["int"],"indexFilterable":true,"indexRangeFilters":false,"indexSearchable":false,"name":"chunk_index"},{"dataType":["text"],"description":"This property was generated by Weaviate's auto-schema feature on Fri Dec 5 05:57:20 2025","indexFilterable":true,"indexRangeFilters":false,"indexSearchable":true,"name":"doc_hash","tokenization":"word"},{"dataType":["uuid"],"description":"This property was generated by Weaviate's auto-schema feature on Fri Dec 5 05:57:20 2025","indexFilterable":true,"indexRangeFilters":false,"indexSearchable":false,"name":"dataset_id"},{"dataType":["text"],"description":"This property was generated by Weaviate's auto-schema feature on Fri Dec 5 05:57:24 2025","indexFilterable":true,"indexRangeFilters":false,"indexSearchable":true,"name":"source","tokenization":"word"}],"replicationConfig":{"asyncEnabled":false,"deletionStrategy":"DeleteOnConflict","factor":1},"shardingConfig":{"actualCount":1,"actualVirtualCount":128,"desiredCount":1,"desiredVirtualCount":128,"function":"murmur3","key":"_id","strategy":"hash","virtualPerPhysical":128},"vectorConfig":{"default":{"vectorIndexConfig":{"bq":{"enabled":false},"cleanupIntervalSeconds":300,"distance":"cosine","dynamicEfFactor":8,"dynamicEfMax":500,"dynamicEfMin":100,"ef":-1,"efConstruction":128,"filterStrategy":"sweeping","flatSearchCutoff":40000,"maxConnections":32,"pq":{"bitCompression":false,"centroids":256,"enabled":false,"encoder":{"distribution":"log-normal","type":"kmeans"},"segments":0,"trainingLimit":100000},"skip":false,"sq":{"enabled":false,"rescoreLimit":20,"trainingLimit":100000},"vectorCacheMaxObjects":1000000000000},"vectorIndexType":"hnsw","vectorizer":{"none":{}}}}}]} ``` I also have the latest version of the StringUUID method. <img width="780" height="431" alt="Image" src="https://github.com/user-attachments/assets/e610989c-d288-42e7-94ed-6472011fe25a" /> But it still reports "Dataset not found. You have requested this URI [/console/api/datasets/98ee35b9-0ca1-4017-9180-f8a85abd9a1e/documents] but did you mean /console/api/datasets/uuid:dataset_id/documents?"
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#20819
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?