Delivery & reliability
Message replay
Message replay sends previously recorded events to a consumer so it can reconstruct state or catch up with changes it did not receive live.
Also found under: Catch-up, Offline recovery
How it works
Replay requires stored events, a way to choose a starting point and a policy for handling repeated or old records. Reopening a network connection does not supply those pieces. Some applications can recover more simply by fetching a fresh snapshot instead of replaying every intermediate event.
In a Pubb integration
Pubb subscriptions should not be treated as an automatic replay stream. Keep history or versioned state in your backend and use it to repair the interface after an offline period.
Connect a clientA practical example
After a dashboard reconnects, request its current totals rather than expecting every missed counter event. A chat app can instead fetch saved messages after its last known message ID.