pnclPULSEGet API access

DROP ALERT NOTES

When the same drop fires on both streams

Live and prematch streams run side by side, and a match crossing phases can alert on both. How to merge cross-stream duplicates without losing the move.

Your live relay and your prematch relay each hold their own stream, and on the day a match crosses from prematch to live, the same falling price can fire on both. Two alerts, one move, zero desire to hear about it twice. Cross-stream dedupe is a small extension of the keys you already run, and here is how to think about it.

Why the duplicate exists at all

The two streams are independent products: each account holds one connection per stream, and the live and prematch streams run side by side, as the SSE setup guide documents, checked 2026-10-19. When a match sits on both boards during the handoff, a price fall that crosses your threshold is detected by both engines, and each writes its own alert with its own id.

The two alerts are not duplicates by the stream's definition: they come from different streams. They are duplicates by yours.

The merge key, not the alert key

Your dedupe store keys on the alert id, and that works within one stream, as the dedupe guide lays out. Across streams, the id differs, so merge on the selection key instead: match, market, side and period, the fields that name what fell rather than which engine saw it. Two alerts with the same selection key inside a short window are the same move, regardless of which stream carried them.

Keep the first, quarantine the second into your decision log as a cross-stream repeat, and let the cooldown from the dedupe guide run on the merged record.

The window that decides

The handoff window is the whole question. A live alert and a prematch alert on the same selection five minutes apart are probably the same move detected twice; the same selection thirty minutes apart is probably two moves on a match in play. Set the merge window from your own log of cross-stream pairs, not from instinct.

The phase boundary is where the streams overlap, and that is where your merge rule earns its keep.

What you must not merge

Different markets on the same match are not duplicates, and different periods are not duplicates, because the selection key already contains both. The merge is only ever about the same selection crossing your threshold on two streams in the same short window. Merge more than that, and you start silencing real moves.

Selection key, short window, first one wins. The two streams will both do their job; your merge rule makes sure you only hear it once.