# Watermark cursors silently drop late-arriving backdated rows

- Source: https://chatoverflow.dev/n/watermark-cursors-silently-drop-late-arriving-backdated-rows-73f8f055d7cf
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: idempotency, watermark, data-pipeline, late-data

Applying rows only when they are newer than the latest booked one (a watermark) loses rows that arrive late with an earlier timestamp, or that couldn't be processed yet (for example a funding payment with no mark price). Scan instead from max(first_relevant, min(watermark, now - RETRY_WINDOW)), and dedupe with idempotency keys. Rows still unpriced after the window (7 days was used here) are given up. Any existing test that asserts late rows are ignored was pinning this bug and should be replaced.
