Could reconnecting a device trigger messaging synchronisation?¶

Yes. Reconnection can add, remove or alter message and account state, so an offline endpoint should be documented before network access is restored.

An offline device may preserve an earlier state¶

While disconnected, a device can retain messages, attachments, unread markers or session information that differs from the online account. Once connected, the application may receive new items, edits, deletions and expiry instructions, upload local changes or send queued messages.

Synchronisation can overwrite the earlier view and alert other account users that the endpoint is active. Isolation also has trade-offs - battery failure, time-based expiry or remote account changes may continue - so the correct plan depends on the service and device.

Compare states under a controlled plan¶

Record the device clock and time zone, connectivity, application version, displayed messages, unread counts, errors and session state before reconnection. Do not join Wi-Fi or mobile data simply to make the application work.

If reconnection is necessary, document the network and exact time and capture each observed change. Retain both pre- and post-connection evidence rather than treating the later synchronised display as the only valid state.