Dead letters
Handle EDFlow dead letters: buffered events that expired and processing errors, viewing and revealing payloads (audited), replaying after a fix, discarding, and bulk replay.
A dead letter is an event EDFlow couldn't apply: a buffered event whose visit never arrived within 6 hours, or a processing error.
Each row
Reason, source, type and received time. The integration on-call is alerted for every new dead letter.
Actions
| Action | Notes |
|---|---|
| View | The allow-listed projection, as in the event log |
| Reveal payload | Shows the full payload. Audited, and counts toward the privacy office's monitoring rule A-1 |
| Replay | After you've fixed the cause (for example mapped a code or the arrival came in). Runs through the normal pipeline; running it twice is safe |
| Discard | With a reason |
| Bulk replay | For many dead letters with the same cause |
Common causes
- The arrival was never sent (check the engine's ADT routing).
- A roster was quarantined by the circuit breaker.
- An identifier change the pipeline couldn't handle (for example a merge sent in an unexpected shape).
Dead letters are kept for 30 days.
Related
Dernière mise à jour le
Cette page vous a-t-elle été utile?
Unmapped codes
Map unmapped test and location codes from the EHR feed in EDFlow: map to a catalogue test, create an entry or ignore, the zero-unmapped go-live gate, and AI mapping suggestions.
Data issues
Work the EDFlow Report a data problem queue: what staff report, resolving or closing reports, and how data issues feed the 98% milestone agreement go-live gate.