pnclPULSEGet API access

DROP ALERT NOTES

The stream is open but silent: quiet market or dead feed

No alerts for hours means a calm market or a dead connection, and the two need opposite responses. A two-minute check tells them apart.

The reader is running, no errors, no alerts, for hours. Either nothing has moved, or the feed is dead while the socket stays politely open. The two silences look identical from the outside and demand opposite responses: one you wait out, the other you fix. Here is the two-minute triage that tells them apart.

Silence is a symptom with two causes

The stream only writes when a price falls past your threshold, as the drop alerts guide sets out, checked 2026-10-26. A genuinely quiet stretch, an empty slate at 4 a.m., an off-season sport, a high min_drop on a calm market, produces exactly the same nothing as a dead connection. Before you touch anything, note that both are normal until proven otherwise.

The dangerous assumption is the one most dashboards bake in: open socket equals live feed. A network path can hold a connection open while delivering nothing for hours, and some proxies do exactly that.

Rule out the self-inflicted silence first

The SSE setup guide documents two properties that explain most mystery silences, checked 2026-10-26. The stream opens with a control object, the connected frame: if your log has no recent connected frame, you are not on the stream at all. And each account gets one connection per stream, so a second connection with the same key closes the first. The classic case is a deploy: the new process connects, the old one's log goes silent, and someone spends an hour debugging the wrong box.

Check the clock too. The connected frame and each alert carry timestamps; a connected frame from yesterday with no alerts since is evidence about the connection, not the market.

Cross-check with the REST drops endpoint

The decisive test costs one request. The REST drops endpoint reports recent drops on demand, so pull it for the window that worried you, with your sport and threshold, as the stream versus endpoint comparison describes the two channels, checked 2026-10-26. Two outcomes:

  • The endpoint shows drops your stream never sent: the stream is the problem. Reconnect, and if silence repeats, treat the connection as suspect even while it stays open.
  • The endpoint is as empty as the stream: the market is genuinely quiet. Your feed is fine; your calendar was the suspect.

Run the check before reconnecting, not after. Once you reconnect, the evidence of what the old connection was doing is gone.

When it really is a quiet market

If the cross-check says quiet, confirm with context. Look at the slate: how many matches are upcoming in the sports your filter allows, and how far from kickoff they sit. Prematch moves cluster toward the close, so a silent afternoon with a full evening card is the market behaving, not the feed failing.

If you want silence to mean something going forward, lower min_drop toward the documented floor of 1 for a day as a probe. A stream that fires on small moves is alive; a stream that stays mute while the endpoint fills up is not, whatever the socket claims.

Silence is data once you know which kind you are looking at. Two minutes, one extra request, and the guesswork is gone.