Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #4608] [BUG]: Client side timeout for gpt-5-pro #2931

New Issue
Closed
opened 2026-02-22 18:31:53 -05:00 by yindo · 3 comments
yindo commented 2026-02-22 18:31:53 -05:00
Owner
Copy Link
Copy Source

Originally created by @danielrehsmann on GitHub (Nov 3, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4608

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

I use the official OpenAI provider.
If I ask a model that takes longer times to respond, I run into a Socket timeout. This seems to be a client side error. See the attached log file

backend-2025-11-03.log

Are there known steps to reproduce?

Use a deep reasoning model and ask a difficult question.

Originally created by @danielrehsmann on GitHub (Nov 3, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4608 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? I use the official OpenAI provider. If I ask a model that takes longer times to respond, I run into a Socket timeout. This seems to be a client side error. See the attached log file [backend-2025-11-03.log](https://github.com/user-attachments/files/23305177/backend-2025-11-03.log) ### Are there known steps to reproduce? Use a deep reasoning model and ask a difficult question.
yindo added the possible bugneeds info / can't replicate labels 2026-02-22 18:31:54 -05:00
yindo closed this issue 2026-02-22 18:31:54 -05:00
yindo commented 2026-02-22 18:31:54 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Nov 20, 2025):

This is likely related to the standard timeout associated with HTTP requests - if you response takes longer than 5mins it will be aborted. This applies as well to the agent responses.

Do you know if this request went on longer than 5 minutes? I presume for reasoning that could be the case. Will re-open on confirmation

@timothycarambat commented on GitHub (Nov 20, 2025): This is likely related to the standard timeout associated with HTTP requests - if you response takes longer than 5mins it will be aborted. This applies as well to the agent responses. Do you know if this request went on longer than 5 minutes? I presume for reasoning that could be the case. Will re-open on confirmation
yindo commented 2026-02-22 18:31:54 -05:00
Author
Owner
Copy Link
Copy Source

@danielrehsmann commented on GitHub (Nov 21, 2025):

This was indeed what was happening. But I think the problem occurs after 10min not 5.

@danielrehsmann commented on GitHub (Nov 21, 2025): This was indeed what was happening. But I think the problem occurs after 10min not 5.
yindo commented 2026-02-22 18:31:54 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Nov 21, 2025):

Patched in commit 3b4f07cdbd

The standard timeout for requests is 300s, so it would have failed around then. After testing, that is how I was able to reproduce. For the interim, I moved timeout to 15min. Future state should be a separate thread/job that can run async totally

@timothycarambat commented on GitHub (Nov 21, 2025): Patched in commit 3b4f07cdbd3a2d2cf71cf7544f58b03472a597ba The standard timeout for requests is 300s, so it would have failed around then. After testing, that is how I was able to reproduce. For the interim, I moved timeout to 15min. Future state should be a separate thread/job that can run async totally
yindo changed title from [BUG]: Client side timeout for gpt-5-pro to [GH-ISSUE #4608] [BUG]: Client side timeout for gpt-5-pro 2026-06-05 14:49:21 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label needs info / can't replicate possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2931
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?