GapDetected: SyncEntity & {
    eventCursor: number;
    localCursor: number;
}

A live event brought a journal seq the local cursor cannot reach in one step.

Purely informational: a gap is not a loss. Records are numbered atomically but delivered out of order, and changes addressed to other members consume numbers this client never sees. The synchronizer checks such an entity with a difference request of its own, see MessagesSyncOptions.gapCheckDelayMs.

A server that sends cursor watermarks closes the second kind on its own, so what is left here is genuinely out of order delivery — rare, and worth a difference request.

Type declaration

  • eventCursor: number
  • localCursor: number