Gemini API error leads to conversation fold when continuing the existing generation

[KiGamji]

Version Information

ghcr.io/danny-avila/librechat-dev latest 6aafee864549 15 hours ago

Steps to Reproduce

2025-02-12.20-50-04.1.mp4

Here I am first making the RPM hit on the second page, while showing how then the error on the first page is shown to be a part of user message history, which is fixed after page refresh (moved to gemini response history), and then another case when the response is being continued from existing response, which is, in case of 429 error, has error shown improperly, and leads to conversation fold.

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

It's not easy to reproduce this, no relevant log outputs from the server were shared, and the title for this issue is misleading and untrue:

Gemini API error leads to conversation fold when continuing the existing generation

Continuing the conversation doesn't lead to this error.

[KiGamji]

It only happens when you get an error during the attempt to continue the conversation.

That's what happens if you simply encounter this during regeneration or new message attempt:

And here's the issue with continuing the existing generation:

The real error gets masked and the conversation folds, namely the error message is put in the beginning as a branch. I have just flooded my key to get 429 error, so it's easier to reproduce.

[danny-avila]

Ok, I can see the issue when I force an error, it should be a simple fix.

[danny-avila]

should be resolved here #5833