From d41b26a6852985e679893034719037dfeca83f7e Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Wed, 29 Apr 2026 10:56:47 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@21a92ea0f636ef5b0f1190136b3bc13e76854754 --- .openclaw-sync/source.json | 4 ++-- docs/channels/whatsapp.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 2fadfec7a..8f1840f0c 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "0c9f84451a9f6074bd9402a18c7dd794f628ce59", - "syncedAt": "2026-04-29T10:48:27.457Z" + "sha": "21a92ea0f636ef5b0f1190136b3bc13e76854754", + "syncedAt": "2026-04-29T10:55:21.901Z" } diff --git a/docs/channels/whatsapp.md b/docs/channels/whatsapp.md index ee055ccf2..18289cfa8 100644 --- a/docs/channels/whatsapp.md +++ b/docs/channels/whatsapp.md @@ -151,7 +151,7 @@ OpenClaw recommends running WhatsApp on a separate number when possible. (The ch ## Runtime model - Gateway owns the WhatsApp socket and reconnect loop. -- The reconnect watchdog uses WhatsApp Web transport activity, not only inbound app-message volume, so a quiet linked-device session is not restarted solely because nobody has sent a message recently. A longer application-silence cap still forces a reconnect if transport frames keep arriving but no application messages are handled for the watchdog window. +- The reconnect watchdog uses WhatsApp Web transport activity, not only inbound app-message volume, so a quiet linked-device session is not restarted solely because nobody has sent a message recently. A longer application-silence cap still forces a reconnect if transport frames keep arriving but no application messages are handled for the watchdog window; after a transient reconnect for a recently active session, that application-silence check uses the normal message timeout for the first recovery window. - Baileys socket timings are explicit under `web.whatsapp.*`: `keepAliveIntervalMs` controls WhatsApp Web application pings, `connectTimeoutMs` controls the opening handshake timeout, and `defaultQueryTimeoutMs` controls Baileys query timeouts. - Outbound sends require an active WhatsApp listener for the target account. - Status and broadcast chats are ignored (`@status`, `@broadcast`).