openclaw - 💡(How to fix) Fix [Bug]: [Bug]: Requests abort after ~1 minute with Request timed out before a response was generated despite agents.defaults.timeoutSeconds set to 18 minutes [2 comments, 3 participants]

agents.defaults.timeoutSeconds is set to 1080 seconds. Observed backend error at the same time is Ollama HTTP 499.

TL;DR

The issue can be mitigated by investigating and adjusting the timeout settings in the OpenClaw configuration and the Ollama model backend to ensure consistency and to identify any overriding timeouts.

Guidance

• Review the OpenClaw configuration to ensure that agents.defaults.timeoutSeconds is correctly set to 1080 seconds and that there are no other timeout settings that could be overriding this value.
• Investigate the Ollama model backend to understand why it is reporting an HTTP 499 error at the same time OpenClaw aborts the request, as this may indicate a timeout or other issue on the backend.
• Verify that the version of Ollama being used (ollama/qwen3.5:27b) does not have a known issue with timeouts or compatibility with OpenClaw version v2026.4.1.
• Consider testing with a different model backend to isolate if the issue is specific to the Ollama backend or a more general issue with OpenClaw.

Example

No specific code example can be provided without more details on the configuration files or codebase, but ensuring the timeout settings are correctly applied in the OpenClaw configuration file (e.g., config.json or similar) is crucial.

Notes

The issue seems to be related to a mismatch or override of the timeout settings between OpenClaw and the Ollama backend. The fact that downgrading is not possible and the software is unusable for longer tasks highlights the need for a prompt resolution.

Recommendation

Apply workaround: Adjust the timeout settings in both OpenClaw and the Ollama model backend to ensure they are consistent and not being overridden, and monitor the behavior to see if the issue persists. This approach is recommended because it directly addresses the potential root cause of the problem without requiring a version upgrade, which may not be feasible given the constraints mentioned.