Live events, history synchronisation and unread reconciliation
Understand the shared long-poll, event cursor, bounded fallback refresh, browser-store recovery, history import and authoritative unread model.
Guides in this workflow
Select the exact setup, Inbox, verification, automation, portal, audit or troubleshooting action you need.
Understand the shared all-account live channel
The Inbox and header use one low-latency wait covering all active accounts the staff member can view.
Understand the 18-second live wait
Know that the installed option bounds the connector wait before the browser renews the request.
Understand fallback Inbox refresh
If long-polling stalls, the configured 4–60 second refresh path recovers visible state.
Configure the Inbox refresh interval
Set a value from 4 to 60 seconds in Settings.
Enable synchronisation when Inbox loads
Turn on Synchronise WhatsApp messages when an inbox loads.
Disable synchronisation on Inbox load
Turn off the page-load pull when cron/live flow is intentionally relied upon.
Enable WhatsApp cron synchronisation
Turn on Synchronise WhatsApp messages through Britixo cron so queued events import while no Inbox is open.
Disable cron synchronisation
Turn off the after-cron sync branch only when another supported live/manual flow is deliberately used.
Run manual history synchronisation
Use Sync history on Connections for the selected account.
Configure the default history chat limit
Set the number of recent chats from 1 to 500.
Configure messages per chat during history sync
Set the per-chat import from 1 to 200.
Understand immediate post-connect history import
After a linked device becomes ready, the connector requests the configured recent chats automatically.
Understand the browser-store compatibility history reader
If normal chat conversion is rejected by the current WhatsApp Web client, a bounded compatibility reader retrieves the recent window.
Understand continuous inbound and outbound ingestion
Native linked-device events are stored as they occur after connection.
Understand missed-message reconciliation
A lightweight browser-store check recovers a recent message missed by the native event hook and deduplicates it.
Understand event cursors
Each account stores its last consumed connector sequence so events are not replayed unnecessarily.
Understand event-stream identity recovery
If the connector event store is recreated and sequence restarts, the changed stream ID triggers a safe cursor reset.
Understand authoritative unread snapshots
The connector publishes WhatsApp browser-store unread counts rather than relying only on local increments.
Understand aggregate unread badges
The header sum includes only active, accessible accounts and excludes soft-deleted accounts.
Troubleshoot a stale unread badge
Open the account, allow live/fallback refresh, verify connector state and use the real mark-read operation rather than manually changing database values.
Understand duplicate-event safety
The same WhatsApp message ID arriving through history, live and reconciliation is stored once.
Understand account-state reconciliation on event pulls
Each pull compares stored connection state with the connector’s current authoritative state.