Operational alerts with recorded send outcomes.
Give operators enough context to act on an alert.
Where this work fits
The schedule said what should play. Reporting needed to know what did play, including when a device lost its connection or a prayer interrupted a track. Sending each record immediately was not always possible.
I connected missed-event monitoring to email alerts and recorded the send result. Failures and missing recipients remained visible rather than being marked as sent. The message carried enough context for an operator to begin investigating.
Schedule a tailored message across channels
Keep the record until delivery succeeds.
Removing a record when sending started could lose it on failure. I retained unsent records on the device and removed the sent batch after success. Monitoring had a related timing problem: it needed to allow for delayed evidence before treating an expected event as missing.
The skills behind the work
- Email integration
- Connect product messages or alerts with a delivery service and handle send outcomes.
- Validation
- Reject invalid or unsupported input before it affects the rest of the application.
- Error recovery
- Handle interruptions and failed operations without discarding useful progress.
Unsent playback records could survive a restart and travel when connectivity returned. Monitoring made missed activity easier to investigate, with alert outcomes recorded separately from the detection itself.