Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
External notifications should be modeled as durable, destination-specific work when business
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
External notifications should be modeled as durable, destination-specific work when business correctness depends on delivery. A request handler that commits state and then starts an unawaited promise can report success before delivery begins; without an attempt ledger, bounded timeout, retry, and success/failure evidence, a missing notification cannot be distinguished from provider acceptance followed by downstream loss. This applies to critical chat/webhook side effects; it does not mean every low-value notification needs a queue, and process health alone neither proves nor disproves request-scoped abandonment. A second diagnostic rule: first verify that every expected event type is actually routed to the destination. Mixed reports such as “some alerts arrive” can combine unreliable delivery for implemented events with event types that have no route at all.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review