github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-12 10:04:14 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

bug: RAG loses context on model response regeneration with Groq models via API key #444

New Issue
Closed
opened 2025-11-11 14:21:31 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 14:21:31 -06:00
Owner
Copy Link

Originally created by @silentoplayz on GitHub (Mar 8, 2024).

Feel free to adjust the title of this bug report, I know it's a terrible one.

Bug Report

Description

Bug Summary: The RAG feature loses context on model response regeneration when using Groq models via the API integration into Open WebUI.

Expected Behavior:
The RAG feature should maintain context and provide consistent responses throughout the conversation, even on model response regeneration.

Actual Behavior:
The RAG feature does not maintain context and provides inconsistent responses throughout the conversation when using Groq models via the API integration into Open WebUI. However, when using a locally installed LLM, the RAG feature is able to maintain context and provide consistent responses throughout the conversation.

Environment

Operating System:
Windows 11 Pro Insider Preview
Version 22H2
Installed on ‎2/‎4/‎2024
OS build 23620.1000
Experience Windows Feature Experience Pack 1000.23620.1000.0

Browser: FireFox v123.0.1 (64-bit)

Reproduction Details

Steps to Reproduce:

  1. Integrate Groq models via the API into Open WebUI
  2. Interact with the RAG feature
  3. Observe the initial response
  4. Regenerate the response
  5. Observe the loss of context in the regenerated response

Confirmation:

  • I have read and followed all the instructions provided in the README.md.
  • I am on the latest version of both Open WebUI and Ollama.

Additional Information

Note: This issue does not occur when using a locally installed LLM. The RAG feature is able to maintain context and provide consistent responses throughout the conversation when using a locally installed LLM. As far as I am aware, this issue is specific to the integration of Groq models via the API in Open WebUI, but it could potentially effect multiple APIs, being any that I don't have access to.

Edit: If anyone could replicate this issue and verify that it is indeed a bug, please share down below in the comments.

Originally created by @silentoplayz on GitHub (Mar 8, 2024). Feel free to adjust the title of this bug report, I know it's a terrible one. # Bug Report ## Description **Bug Summary:** The RAG feature loses context on model response regeneration when using Groq models via the API integration into Open WebUI. **Expected Behavior:** The RAG feature should maintain context and provide consistent responses throughout the conversation, even on model response regeneration. **Actual Behavior:** The RAG feature does not maintain context and provides inconsistent responses throughout the conversation when using Groq models via the API integration into Open WebUI. However, when using a locally installed LLM, the RAG feature is able to maintain context and provide consistent responses throughout the conversation. ## Environment **Operating System:** Windows 11 Pro Insider Preview Version 22H2 Installed on ‎2/‎4/‎2024 OS build 23620.1000 Experience Windows Feature Experience Pack 1000.23620.1000.0 **Browser:** FireFox v123.0.1 (64-bit) ## Reproduction Details **Steps to Reproduce:** 1. Integrate Groq models via the API into Open WebUI 2. Interact with the RAG feature 3. Observe the initial response 4. Regenerate the response 5. Observe the loss of context in the regenerated response **Confirmation:** - [x] I have read and followed all the instructions provided in the README.md. - [x] I am on the latest version of both Open WebUI and Ollama. ## Additional Information **Note:** This issue does not occur when using a locally installed LLM. The RAG feature is able to maintain context and provide consistent responses throughout the conversation when using a locally installed LLM. As far as I am aware, this issue is specific to the integration of Groq models via the API in Open WebUI, but it could potentially effect multiple APIs, being any that I don't have access to. Edit: If anyone could replicate this issue and verify that it is indeed a bug, please share down below in the comments.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#444
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?