1. Describe the bug
When message processing fails in the WhatsApp bot, it tries to notify the user with an error message. If that send also fails (expired token, rate limit, network problem), a bare except: pass at whatsapp_bot.py:460 eats the exception. Nothing gets logged. If WhatsApp sends are broken across the board, users stop getting responses and there's zero signal in the logs about why.
2. To reproduce
- Start the WhatsApp bot
- Trigger a processing error (e.g., point it at a dead MCP server)
- Revoke the WhatsApp access token so sends fail too
- Check logs — the original processing error is there, but the failed notification attempt isn't
3. Expected behavior
The failed send should show up in logs. Something like logger.error(f"Failed to notify user: {e}").
4. Environment
- Affected MCP Server Name: mcp-clients (WhatsApp bot)
- MCP Server Version/Commit: main HEAD
- Klavis Service:
1. Describe the bug
When message processing fails in the WhatsApp bot, it tries to notify the user with an error message. If that send also fails (expired token, rate limit, network problem), a bare
except: passatwhatsapp_bot.py:460eats the exception. Nothing gets logged. If WhatsApp sends are broken across the board, users stop getting responses and there's zero signal in the logs about why.2. To reproduce
3. Expected behavior
The failed send should show up in logs. Something like
logger.error(f"Failed to notify user: {e}").4. Environment