Summary

WhatsApp channel periodically disconnects with status 499 or sync errors after being connected for an extended period.

Steps to reproduce

1. Link WhatsApp channel via QR code.
2. Maintain active gateway for 12+ hours.
3. Observe gateway logs for status 499 or "registered: false" errors.
4. Channel becomes unresponsive until manual gateway restart.

Expected behavior

The WhatsApp connection should remain persistent and automatically re-authenticate/re-connect without requiring a full gateway restart.

Actual behavior

Gateway logs show status 499 and session becomes unlinked or "registered: false" in status output.
System: [2026-02-16 00:10:22 GMT+8] WhatsApp gateway disconnected (status 499)
System: [2026-02-16 00:10:40 GMT+8] WhatsApp gateway connected. (Though often it remains degraded)

OpenClaw version

2026.2.14

Operating system

Windows 11 / Windows Server 2025 (NT 10.0.26200)

Install method

npm global / scheduled task service

Logs, screenshots, and evidence

Impact and severity

Affected: WhatsApp channel users.
Severity: High (blocks proactive messaging and heartbeats).
Frequency: Intermittent, typically after 8-12 hours of uptime.
Consequence: Missed messages and failed automation runs.

Additional information

Environment is running Node.js 22.16.0 on Windows. The issue seems related to session persistence or token refresh logic in the WhatsApp provider. Also seeing frequent "spawnSync /bin/sh ENOENT" logs in Windows environment when running 'openclaw status'.