[GH-ISSUE #5624] auto retry function #101054

Closed
opened 2026-05-17 22:42:14 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @123hi123 on GitHub (Sep 23, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/5624

Is your feature request related to a problem? Please describe.
The O1 model is extremely unstable when processing requests. Users currently have to manually retry multiple times until they get a correct response from the O1 model, which is frustrating and time-consuming.

Describe the solution you'd like
I would like to add an automatic retry functionality. This feature would allow users to set a number of retry attempts. The system would then automatically retry the request up to the specified number of times, without requiring manual intervention from the user, until a correct response is received from the O1 model.

Describe alternatives you've considered
An alternative could be to implement a queueing system that holds failed requests and retries them in the background. However, this might not provide immediate feedback to the user.

Additional context
This feature would significantly improve user experience, especially when dealing with unstable models like O1. It would save users time and reduce frustration caused by manual retries.

Originally created by @123hi123 on GitHub (Sep 23, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/5624 **Is your feature request related to a problem? Please describe.** The O1 model is extremely unstable when processing requests. Users currently have to manually retry multiple times until they get a correct response from the O1 model, which is frustrating and time-consuming. **Describe the solution you'd like** I would like to add an automatic retry functionality. This feature would allow users to set a number of retry attempts. The system would then automatically retry the request up to the specified number of times, without requiring manual intervention from the user, until a correct response is received from the O1 model. **Describe alternatives you've considered** An alternative could be to implement a queueing system that holds failed requests and retries them in the background. However, this might not provide immediate feedback to the user. **Additional context** This feature would significantly improve user experience, especially when dealing with unstable models like O1. It would save users time and reduce frustration caused by manual retries.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#101054