[GH-ISSUE #1441] [BUG]: Issues with Recording Knowledge in the Database #919

Closed
opened 2026-02-22 18:22:12 -05:00 by yindo · 2 comments
Owner

Originally created by @chalitbkb on GitHub (May 17, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1441

How are you running AnythingLLM?

Docker (local)

What happened?

The content contains special characters, making it impossible to save in the knowledge database.
image

Are there known steps to reproduce?

No response

Originally created by @chalitbkb on GitHub (May 17, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1441 ### How are you running AnythingLLM? Docker (local) ### What happened? The content contains special characters, making it impossible to save in the knowledge database. ![image](https://github.com/Mintplex-Labs/anything-llm/assets/32437546/5891b774-9fbc-4ab9-9b5f-5f8295810cf1) ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:22:12 -05:00
yindo closed this issue 2026-02-22 18:22:12 -05:00
Author
Owner

@timothycarambat commented on GitHub (May 17, 2024):

This is not what that error means. This means the backend crashed while processing the document. Are you running this locally on Docker or using some other service like Render or Railway to run this?

Often, this can happen if the container reaches its CPU/memory limit and kills the background process for the collector script.

@timothycarambat commented on GitHub (May 17, 2024): This is not what that error means. This means the backend crashed while processing the document. Are you running this locally on Docker or using some other service like Render or Railway to run this? Often, this can happen if the container reaches its CPU/memory limit and kills the background process for the collector script.
Author
Owner

@chalitbkb commented on GitHub (May 17, 2024):

This is not what that error means. This means the backend crashed while processing the document. Are you running this locally on Docker or using some other service like Render or Railway to run this?

Often, this can happen if the container reaches its CPU/memory limit and kills the background process for the collector script.

Okay.

But!

It seems that when an unexpected error occurred, the data was not deleted, even though I had already removed it from the "My Documents" page. Perhaps some additional conditions need to be added to the process.

image

image

@chalitbkb commented on GitHub (May 17, 2024): > This is not what that error means. This means the backend crashed while processing the document. Are you running this locally on Docker or using some other service like Render or Railway to run this? > > Often, this can happen if the container reaches its CPU/memory limit and kills the background process for the collector script. Okay. But! It seems that when an unexpected error occurred, the data was not deleted, even though I had already removed it from the "My Documents" page. Perhaps some additional conditions need to be added to the process. ![image](https://github.com/Mintplex-Labs/anything-llm/assets/32437546/992b7b3d-d392-4802-ab17-4a53dee0a4c1) ![image](https://github.com/Mintplex-Labs/anything-llm/assets/32437546/8545c735-8ba2-4e75-8d8e-4f2964ad2372)
yindo changed title from [BUG]: Issues with Recording Knowledge in the Database to [GH-ISSUE #1441] [BUG]: Issues with Recording Knowledge in the Database 2026-06-05 14:37:57 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#919