Replaying Events

Scenario: Due to a temporary network outage, the CRM system missed several events emitted by the OHIP Streaming API. To ensure data integrity, the system must replay and process the missed events.

Conceptual Flow:

1. Reconnection: Once the CRM system restores its connection to the Streaming API, it sends a subscription request with the "offset" parameter set to the last successfully processed event offset.
2. Event Replay: The Streaming API replays all events from the specified offset, allowing the CRM system to process any missed events.
3. Resumption of Real-Time Processing: After catching up, the CRM system continues to process new events in real-time.

Replay logic is single-consumer and strictly ordered per stream. You are responsible for idempotency and duplicate suppression if retries/duplicates occur.

Figure 4-2 Flow Diagram