openclaw - 💡(How to fix) Fix [Bug]: WhatsApp behavior seems to depend on read receipts being enabled [1 comments, 2 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#70470Fetched 2026-04-24 05:57:40
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×2commented ×1

n my tests, OpenClaw behaved inconsistently depending on whether the WhatsApp account had read receipts enabled.

Root Cause

n my tests, OpenClaw behaved inconsistently depending on whether the WhatsApp account had read receipts enabled.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

n my tests, OpenClaw behaved inconsistently depending on whether the WhatsApp account had read receipts enabled.

Steps to reproduce

Set up OpenClaw with WhatsApp linked and working Configure a working Google Calendar integration From a WhatsApp account with read receipts disabled, send a message asking to schedule something at a specific date/time Observe whether the agent fails to verify or create the calendar event properly Enable read receipts on that same WhatsApp account Repeat the same test Observe that the behavior starts working

Expected behavior

The agent should be able to process messages, check Google Calendar, and create calendar events regardless of whether read receipts are enabled or disabled in the sender’s WhatsApp settings.

Actual behavior

When testing with one WhatsApp account that had read receipts disabled, the agent failed to properly verify Google Calendar availability and failed to schedule events correctly. When I enabled read receipts on that same WhatsApp account, the behavior started working correctly.

OpenClaw version

OpenClaw version: 2026.4.21

Operating system

macOS 26

Install method

npm global

Model

openai/chatgpt-5.4-codex

Provider / routing chain

Calendar integration: Zapier + Google Calendar

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

What I tested

Two different WhatsApp accounts Same OpenClaw instance Same general type of message/request New/clean chats Zapier + Google Calendar integration was working from the main session WhatsApp channel itself was linked and working Observed pattern

Account A: worked correctly Account B: failed to verify/schedule After enabling read receipts on Account B: it started working Why this seems wrong

As far as I understand, read receipts should not affect whether OpenClaw can receive, interpret, or act on messages through WhatsApp. This makes it look like there may be a bug or an unexpected dependency in the WhatsApp channel behavior.

extent analysis

TL;DR

The issue may be resolved by modifying the WhatsApp channel integration in OpenClaw to handle messages independently of the sender's read receipts setting.

Guidance

  • Investigate the WhatsApp channel implementation in OpenClaw to identify potential dependencies on read receipts.
  • Verify that the Zapier + Google Calendar integration works consistently across different WhatsApp accounts with read receipts enabled or disabled.
  • Test the OpenClaw instance with multiple WhatsApp accounts and various read receipts settings to confirm the observed pattern.
  • Check the OpenClaw documentation and code for any mentions of read receipts affecting message processing or calendar event creation.

Example

No code snippet is provided as the issue lacks specific technical details about the OpenClaw implementation.

Notes

The root cause of the issue is unclear, and further investigation is needed to determine why read receipts affect the OpenClaw behavior. The provided information suggests a potential bug or unexpected dependency in the WhatsApp channel integration.

Recommendation

Apply a workaround by modifying the WhatsApp channel integration to handle messages independently of the sender's read receipts setting, as the root cause is unclear and may require further investigation.

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…

FAQ

Expected behavior

The agent should be able to process messages, check Google Calendar, and create calendar events regardless of whether read receipts are enabled or disabled in the sender’s WhatsApp settings.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING