Legacy/normal endpoints do not support OCR files. #6580
Replies: 2 comments 3 replies
-
This is by design. Everything will move to agents eventually |
Beta Was this translation helpful? Give feedback.
-
Hey, just jumping in because I’ve seen this OCR-related frustration pop up in multiple LibreChat + RAG threads recently. This issue — where OCR-based content doesn’t work properly with certain endpoints — is actually a known failure mode we’ve catalogued in our open-source diagnostic map. In this specific case, it's Failure Mode No.14–16 — related to undeployed or misaligned upstream components like unready OCR parsing, endpoint routing mismatch, or schema desync between front/backend. I’ve run into and fixed these in production pipelines, so we created a complete list + corresponding fixes: 🔗 [WFGY ProblemMap – Full diagnostic map with real solutions] And since OCR is central to many of these cases —
If you're stuck trying to wire OCR + RAG + agent routing together, this might help avoid months of debugging. Let me know if you want a pointer to the specific workaround we used for endpoint handoff + OCR ingestion. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
What happened?
The problem is that only on normal endpoints (not agents) files that have gone through OCR show an error message when trying to interact. I have done the same process with the agent endpoint and it works correctly.
Interaction with error (normal/legacy endpoints)

Correct interaction (agents endpoints)
In the Gemini endpoint, the error does not appear but instead the context is not taken into account, the model does not know what I am talking about:
Version Information
docker images | grep librechat
:Steps to Reproduce
What browsers are you seeing the problem on?
Firefox
Relevant log output
Screenshots
No response
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions