1. error occur no error {"ts":"2026-04-11T06:42:38.569Z","severity":"ERROR","service":"langgenius/dify","caller":"batch_clean_document_task.py:85","message":"Failed to clean vector index for dataset_id: 0561270c-6024-4c07-bf8e-bc68f6972622, document_ids: ['243e9451-e370-4017-9a32-b31110e21115', '2a2c2961-5f67-4034-afb3-173f2fc87a60', '2f8571ec-36b2-4715-b4fc-ad1925e598e3', '42a9d049-8194-4dd1-b9b7-39f434b8076b', '4e3cd7bc-57df-4d63-b35d-ac35a05ce9a9', '76372b36-e4a0-4813-8d47-142318d7f066', '7e1628b6-30d0-463c-a17e-f4ad3eab69ea', '86720383-c978-4513-bc7a-b3e75c096400', '874f1f6e-7dc1-4257-873d-fd191d396e19', '914d920a-5dc6-418c-a398-397abd89fbf9', '94bfba04-4918-4b17-a6dd-1ecf3319f846', 'aaf539f1-f979-4859-b2d7-92b96e1d7409', 'c7962cd2-1138-4ca2-8b76-5ff055108b27'], index_node_ids count: 8546","trace_id":"4e1072e9ecb15407840e468ff2d57130","stack_trace":"Traceback (most recent call last):\n File "/app/api/tasks/batch_clean_document_task.py", line 81, in batch_clean_document_task\n index_processor.clean(\n File "/app/api/core/rag/index_processor/processor/parent_child_index_processor.py", line 194, in clean\n vector.delete_by_ids(child_node_ids)\n File "/app/api/core/rag/datasource/vdb/vector_factory.py", line 270, in delete_by_ids\n self._vector_processor.delete_by_ids(ids)\n File "/app/api/core/rag/datasource/vdb/tidb_on_qdrant/tidb_on_qdrant_vector.py", line 310, in delete_by_ids\n raise e\n File "/app/api/core/rag/datasource/vdb/tidb_on_qdrant/tidb_on_qdrant_vector.py", line 300, in delete_by_ids\n self._client.delete(\n File "/app/api/.venv/lib/python3.12/site-packages/qdrant_client/qdrant_client.py", line 1201, in delete\n return self._client.delete(\n ^^^^^^^^^^^^^^^^^^^^\n File "/app/api/.venv/lib/python3.12/site-packages/qdrant_client/qdrant_remote.py", line 1700, in delete\n result: Optional[types.UpdateResult] = self.openapi_client.points_api.delete_points(\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/app/api/.venv/lib/python3.12/site-packages/qdrant_client/http/api/points_api.py", line 1173, in delete_points\n return self._build_for_delete_points(\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/app/api/.venv/lib/python3.12/site-packages/qdrant_client/http/api/points_api.py", line 206, in build_for_delete_points\n return self.api_client.request(\n ^^^^^^^^^^^^^^^^^^^^^^^^\n File "/app/api/.venv/lib/python3.12/site-packages/qdrant_client/http/api_client.py", line 76, in request\n return self.send(request, type)\n ^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/app/api/.venv/lib/python3.12/site-packages/qdrant_client/http/api_client.py", line 99, in send\n raise UnexpectedResponse.for_response(response)\nqdrant_client.http.exceptions.UnexpectedResponse: Unexpected Response: 500 (Internal Server Error)\nRaw response content:\nb'{"time":5e-8,"status":{"error":"Internal server error: [trace-id:662e6390-660c-4242-8071-63a02c681538] database error"}}'\n"}

TL;DR

The issue is likely caused by a database error when trying to delete vector indexes, resulting in an internal server error.

Guidance

• The error message indicates a database error, specifically an internal server error, when trying to delete points from the Qdrant database.
• The delete_by_ids method in tidb_on_qdrant_vector.py is raising an exception, which suggests that the issue may be related to the Qdrant client or the database connection.
• To mitigate the issue, you can try to:
  • Check the Qdrant database logs for any errors or issues related to the delete operation.
  • Verify that the Qdrant client is properly configured and connected to the database.
  • Consider implementing retry logic or error handling for the delete_by_ids method to handle temporary database errors.

Example

No code example is provided as the issue is related to a specific database error and requires further investigation.

Notes

The issue may be related to a bug in the Qdrant client or the database itself, and further investigation is required to determine the root cause.

Recommendation

Apply workaround: Implement retry logic or error handling for the delete_by_ids method to handle temporary database errors, as this may help mitigate the issue until the root cause is determined.