#OpenClaw just answering with: "⚠️ Something went wrong while processing your request. Please try ag"
1 messages · Page 1 of 1 (latest)
15:10:06+00:00 warn agent/embedded {"subsystem":"agent/embedded"} {"event":"embedded_run_agent_end","tags":["error_handling","lifecycle","agent_end","assistant_error"],"runId":"0acfc36c-4612-438b-b5b6-031e59c9e4a7","isError":true,"error":"⚠️ API rate limit reached. Please try again later.","failoverReason":"rate_limit","model":"gemini-2.5-flash","provider":"google","rawErrorPreview":"{"error":{"message":"{\n \"error\": {\n \"code\": 429,\n \"message\": \"You exceeded your current quota, please check your plan and billing details. For more information on this error, head to: https://ai.google.dev/gemini-api/docs/rate-limits. To monitor your current usage, head to: https://ai.dev/rate-limit. \\n* Quota exceeded for metric: generativelanguage.googleapis.com/generate_conten…","rawErrorHash":"sha256:9d3e0f314e8d","rawErrorFingerprint":"sha256:95d2ea7161b1","providerRuntimeFailureKind":"rate_limit","providerErrorMessagePreview":"{\n "error": {\n "code": 429,\n "message": "You exceeded your current quota, please check your plan and billing details. For more information on this error, head to: https://ai.google.dev/gemini-a…"} embedded run agent end
15:10:06+00:00 warn agent/embedded {"subsystem":"agent/embedded"} {"event":"auth_profile_failure_state_updated","tags":["error_handling","auth_profiles","cooldown"],"runId":"0acfc36c-4612-438b-b5b6-031e59c9e4a7","profileId":"sha256:a94403a4f9d0","provider":"google","reason":"rate_limit","windowType":"cooldown","windowReused":false,"previousErrorCount":2,"errorCount":1,"previousCooldownUntil":1776870595258,"cooldownUntil":1776870636454,"failureCounts":{"rate_limit":1}} auth profile failure state updated
15:10:06+00:00 warn agent/embedded {"subsystem":"agent/embedded"} {"event":"embedded_run_failover_decision","tags":["error_handling","failover","assistant","fallback_model"],"runId":"0acfc36c-4612-438b-b5b6-031e59c9e4a7","stage":"assistant","decision":"fallback_model","failoverReason":"rate_limit","profileFailureReason":"rate_limit","provider":"google","model":"gemini-2.5-flash","sourceProvider":"google","sourceModel":"gemini-2.5-flash","profileId":"sha256:a94403a4f9d0","fallbackConfigured":true,"timedOut":false,"aborted":false,"status":429,"rawErrorPreview":"{"error":{"message":"{\n \"error\": {\n \"code\": 429,\n \"message\": \"You exceeded your current quota, please check your plan and billing details. For more information on this error, head to: https://ai.google.dev/gemini-api/docs/rate-limits. To monitor your current usage, head to: https://ai.dev/rate-limit. \\n* Quota exceeded for metric: generativelanguage.googleapis.com/generate_conten…","rawErrorHash":"sha256:9d3e0f314e8d","rawErrorFingerprint":"sha256:95d2ea7161b1","providerRuntimeFailureKind":"rate_limit","providerErrorMessagePreview":"{\n "error": {\n "code": 429,\n "message": "You exceeded your current quota, please check your plan and billing details. For more information on this error, head to: https://ai.google.dev/gemini-a…"} embedded run failover decision
15:10:06+00:00 error diagnostic {"subsystem":"diagnostic"} lane task error: lane=main durationMs=15212 error="FailoverError: ⚠️ API rate limit reached. Please try again later."
15:10:06+00:00 error diagnostic {"subsystem":"diagnostic"} lane task error: lane=session:agent:main:telegram:direct:8736947311 durationMs=15214 error="FailoverError: ⚠️ API rate limit reached. Please try again later."
15:10:06+00:00 warn model-fallback/decision {"subsystem":"model-fallback/decision"} {"event":"model_fallback_decision","tags":["error_handling","model_fallback","candidate_failed"],"runId":"0acfc36c-4612-438b-b5b6-031e59c9e4a7","decision":"candidate_failed","requestedProvider":"groq","requestedModel":"groq/compound-mini","candidateProvider":"google","candidateModel":"gemini-2.5-flash","attempt":2,"total":2,"reason":"rate_limit","status":429,"errorPreview":"⚠️ API rate limit reached. Please try again later.","errorHash":"sha256:2a33d7700899","isPrimary":false,"requestedModelMatched":false,"fallbackConfigured":true} model fallback decision
15:10:06+00:00 error Embedded agent failed before reply: All models failed (2): groq/groq/compound-mini: LLM request failed: provider rejected the request schema or tool payload. (format) | google/gemini-2.5-flash: ⚠️ API rate limit reached. Please try again later. (rate_limit) | ⚠️ API rate limit reached. Please try again later.
15:10:09+00:00 warn telegram/network {"subsystem":"telegram/network"} fetch fallback: DNS-resolved IP unreachable; trying alternative Telegram API IP (codes=UND_ERR_SOCKET)
15:10:09+00:00 warn [telegram] fetch fallback: DNS-resolved IP unreachable; trying alternative Telegram API IP (codes=UND_ERR_SOCKET)
15:10:14+00:00 warn bonjour {"subsystem":"bonjour"} watchdog detected non-announced service; attempting re-advertise (gateway fqdn=openclaw (4)._openclaw-gw._tcp.local. host=openclaw-(4).local. port=18789 state=probing)
15:11:14+00:00 warn bonjour {"subsystem":"bonjour"} watchdog detected non-announced service; attempting re-advertise (gateway fqdn=openclaw (4)._openclaw-gw._tcp.local. host=openclaw-(4).local. port=18789 state=probing)
15:12:14+00:00 warn bonjour {"subsystem":"bonjour"} watchdog detected non-announced service; attempting re-advertise (gateway fqdn=openclaw (4)._openclaw-gw._tcp.local. host=openclaw-(4).local. port=18789 state=probing)
@slate linden
I am using OpenClaw on ProxMox as an LXC! I'm on version 2026.4.15. Here are the latest logs:
It states quite clearly in the log what is wrong.
"API rate limit reached. Please try again later.","failoverReason":"rate_limit","model":"gemini-2.5-flash","provider":"google","rawErrorPreview":"{"error":{"message":"{\n "error": {\n "code": 429,\n "message": "**You exceeded your current quota, please check your plan and billing details. **
Odd. Grok seems to be hitting a different error though:
groq/groq/compound-mini: LLM request failed: provider rejected the request schema or tool payload.
Not really, no. “Over 8B” is way too rough a rule.
For OpenClaw, what matters more is:
- tool calling reliability
- JSON/schema obedience
- long context handling
- whether it stays coherent across multi-step agent loops
So a bigger model can still be annoying if it fumbles tools.
My honest take: if you want reliable agentic behavior, especially with tools, browser, or file ops, I’d still treat Anthropic as the safer baseline right now. Groq can be great for speed, but I would test it against your real workflows instead of picking by parameter count.
Practical rule:
- Simple chat / lightweight assistant stuff: Groq can be fine
- Heavy tool use / multi-step automation: use the strongest tool-reliable option you have, and keep a better fallback