openclaw - 💡(How to fix) Fix feat: Add silentErrorReplies / suppressAgentErrors support for WhatsApp channel [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#59782Fetched 2026-04-08 02:40:34
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
referenced ×3
  • WhatsApp DMs with business contacts who receive confusing error messages
  • Primary model rate limits cascade to fallback model TPM limits
  • The "/new" suggestion is meaningless on WhatsApp

Error Message

When the primary model (e.g., Anthropic Claude) is rate-limited or overloaded and the fallback model also fails, OpenClaw sends a generic error message to the user:

  • buildExternalRunFailureText() in agent-runner.runtime always returns the error message
  1. messages.silentErrorReplies: true — suppress error messages entirely (silent fail)
  2. messages.errorMessage: "..." — custom error text instead of the generic one
  • WhatsApp DMs with business contacts who receive confusing error messages

Root Cause

  • WhatsApp DMs with business contacts who receive confusing error messages
  • Primary model rate limits cascade to fallback model TPM limits
  • The "/new" suggestion is meaningless on WhatsApp
RAW_BUFFERClick to expand / collapse

Feature Request

Problem

When the primary model (e.g., Anthropic Claude) is rate-limited or overloaded and the fallback model also fails, OpenClaw sends a generic error message to the user:

⚠️ Something went wrong while processing your request. Please try again, or use /new to start a fresh session.

This is jarring for non-technical users (e.g., business contacts using WhatsApp) who have no idea what "/new" means or why the bot broke. The Telegram channel has silentErrorReplies but WhatsApp has no equivalent.

Current behavior

  • buildExternalRunFailureText() in agent-runner.runtime always returns the error message
  • The message is delivered to WhatsApp with no way to suppress it
  • messages.suppressToolErrors only covers tool-level warnings, not agent run failures
  • silentErrorReplies only exists in the Telegram config path

Desired behavior

A config option (either global under messages or per-channel) to suppress or customize the agent failure message on WhatsApp. Options could include:

  1. messages.silentErrorReplies: true — suppress error messages entirely (silent fail)
  2. messages.errorMessage: "..." — custom error text instead of the generic one
  3. Per-channel silentErrorReplies support (WhatsApp, Signal, etc.)

The agent should ideally retry silently and only surface errors to the operator (logs), not the end user.

Context

  • WhatsApp DMs with business contacts who receive confusing error messages
  • Primary model rate limits cascade to fallback model TPM limits
  • The "/new" suggestion is meaningless on WhatsApp

Environment

  • OpenClaw 2026.4.1
  • WhatsApp channel
  • Primary: anthropic/claude-opus-4, Fallback: openai/gpt-4o

extent analysis

TL;DR

Implement a config option to suppress or customize the agent failure message on WhatsApp, such as messages.silentErrorReplies or messages.errorMessage, to improve user experience.

Guidance

  • Introduce a new config option under messages to control error message behavior on WhatsApp, e.g., messages.whatsapp.silentErrorReplies or messages.whatsapp.errorMessage.
  • Modify buildExternalRunFailureText() in agent-runner.runtime to respect the new config option and suppress or customize the error message accordingly.
  • Consider adding per-channel support for silentErrorReplies to allow for more flexibility in error handling across different channels.
  • Update the logging mechanism to surface errors to the operator (logs) instead of the end user, ensuring silent retries.

Example

// Example config snippet
messages: {
  whatsapp: {
    silentErrorReplies: true, // or
    errorMessage: "Sorry, we're experiencing technical difficulties. Please try again later."
  }
}

Notes

The proposed solution assumes that the existing silentErrorReplies feature in the Telegram config path can be extended to WhatsApp, and that the buildExternalRunFailureText() function can be modified to respect the new config option.

Recommendation

Apply a workaround by introducing a custom config option to suppress or customize the error message on WhatsApp, as this will allow for a more user-friendly experience while the primary and fallback models are rate-limited or overloaded.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix feat: Add silentErrorReplies / suppressAgentErrors support for WhatsApp channel [1 participants]