github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-11 18:43:44 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #1376] feat: backend timeout error handling #99461

New Issue
Closed
opened 2026-05-17 21:28:27 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-17 21:28:27 -05:00
Owner
Copy Link

Originally created by @shaul75 on GitHub (Apr 1, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/1376

Description

Whenever the API request to the backend takes a while to return any data (usually because the model wasn't loaded yet), and there's a "504 Gateway Time-out" error, the client does not handle it and the user would see the loading skeleton indefinitely, with no indication of a problem unless you open the dev tools.

I suggest adding error handling that'll show a failure message and a retry button to make it clear the request to the backend failed.

Originally created by @shaul75 on GitHub (Apr 1, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/1376 ## Description Whenever the API request to the backend takes a while to return any data (usually because the model wasn't loaded yet), and there's a "504 Gateway Time-out" error, the client does not handle it and the user would see the loading skeleton indefinitely, with no indication of a problem unless you open the dev tools. I suggest adding error handling that'll show a failure message and a retry button to make it clear the request to the backend failed.
GiteaMirror commented 2026-05-17 21:28:29 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Apr 1, 2024):

Steps to reproduce would be extremely helpful here!

<!-- gh-comment-id:2029357390 --> @tjbck commented on GitHub (Apr 1, 2024): Steps to reproduce would be extremely helpful here!
GiteaMirror commented 2026-05-17 21:28:30 -05:00
Author
Owner
Copy Link

@shaul75 commented on GitHub (Apr 1, 2024):

Steps to reproduce would be extremely helpful here!

I don't know of an easy way to force the backend to return 504 there, for me it happens pretty consistently when loading large LLMs (>20GB) during the first chat message.

I can look into it and create a PR myself when I have some free time (probably later today).
I've seen other response codes are already handled in the UI so it should be a small fix

<!-- gh-comment-id:2029418459 --> @shaul75 commented on GitHub (Apr 1, 2024): > Steps to reproduce would be extremely helpful here! I don't know of an easy way to force the backend to return 504 there, for me it happens pretty consistently when loading large LLMs (>20GB) during the first chat message. I can look into it and create a PR myself when I have some free time (probably later today). I've seen other response codes are already handled in the UI so it should be a small fix
GiteaMirror commented 2026-05-17 21:28:31 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Apr 19, 2024):

Closing in favour of #1611

<!-- gh-comment-id:2066389320 --> @tjbck commented on GitHub (Apr 19, 2024): Closing in favour of #1611
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
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#99461
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?