How to synchronize historical messages?

[BabaMing]

sockr.ev.on('messaging-history.set', ({
chats: newChats,
contacts: newContacts,
messages: newMessages,
syncType
}) => {
console.log('messaging-history.set历史', newChats, newContacts, newMessages, syncType);

  // handle the chats, contacts and messages
})

Do not trigger！！ How to solve？？？

[github-actions]

This issue is stale because it has been open for 14 days with no activity. Remove the stale label or comment or this will be closed in 14 days.

[leninpkg]

Its only triggered just after you scanned the qr-code, make sure you dont have:
shouldSyncHistoryMessage: false
or
syncFullHistory: false
in your makeWASocket() call parameters

[github-actions]

This issue is stale because it has been open for 14 days with no activity. Remove the stale label or comment or this will be closed in 14 days.

[alessandropcostabr]

A practical clarification from production usage: messaging-history.set is not a normal realtime event. It is a history rehydration event that usually happens around the initial device sync flow (for example right after QR linking / fresh MD sync), not during ordinary steady-state message reception.

A few things we learned the hard way:

1. It will not behave like messages.upsert.
2. If you disable history sync at socket level, you will never see it.
3. Even when it fires, the payload may contain old messages with provider_timestamp far older than the moment your app receives them.
4. Some synced messages may come in @lid addressing mode, so your storage path must handle LID/PN normalization instead of assuming only @s.whatsapp.net.

The minimum config to avoid accidentally suppressing it is along these lines:

const sock = makeWASocket({
  syncFullHistory: true,
  shouldSyncHistoryMessage: () => true,
})

sock.ev.on('messaging-history.set', ({ contacts, messages, syncType }) => {
  console.log('history sync', { count: messages?.length || 0, syncType })
})

Two important caveats:

• If the session is already established and there is no new history sync cycle, you should not expect this event to keep firing.
• If your code filters too aggressively or assumes only PN JIDs, you may think the event "never fired" when in practice your handler discarded the payload.

We have production evidence of this distinction: one synced WhatsApp message originally dated August 31, 2024 10:23:02 was only inserted into our database on February 13, 2026 12:45:07, with source recorded as history_sync / messaging-history.set. So for debugging, it helps to log both:

• the original message timestamp
• the local insertion/processing timestamp

Short version: if messaging-history.set is not firing for you, first validate these points:

1. syncFullHistory is enabled.
2. shouldSyncHistoryMessage is not returning false.
3. You are testing right after QR linking / fresh sync, not during normal steady-state operation.
4. Your handler is not discarding @lid, status, or other non-PN payloads before logging them.

[github-actions]

This issue is stale because it has been open for 14 days with no activity. Remove the stale label or comment or this will be closed in 14 days.