Delivery Health
A comprehensive guide to understanding Delivery Health monitoring, failure diagnostics, and outbox reliability in Login AlertX.
Overview
A security alert system is only as good as its delivery reliability. If an expired SMTP app password, a revoked webhook token, or an exhausted messaging quota silently blocks your alerts, you could remain unaware of unauthorized physical or remote workstation access.
Introduced in Login AlertX v4.3.0 and further refined in v4.4.0, the Delivery Health Monitoring engine proactively tracks the real-time operational status of every configured notification channel. If an alert fails to reach its destination, Login AlertX diagnoses the exact failure reason and provides one-click navigation to resolve it.
How Delivery Health Works
1. Per-Channel Telemetry
Tracks consecutive failure counters, timestamp of last successful delivery, and exact upstream HTTP/SMTP error responses for every channel.
2. Live Tray Tooltips
Hovering over the Windows system tray icon provides instant status. Shows active alert stats when healthy, and warns “X channel issue(s) detected” when delivery degrades.
3. 1-Click Fix Shortcuts
The Dashboard’s Delivery Health panel displays a direct “Fix Settings” button next to any degraded channel, routing you straight to the exact field needing attention.
Actionable Failure Diagnostics
Rather than presenting vague “Delivery Failed” messages, Login AlertX inspects low-level protocol responses to pinpoint the root cause:
| Channel | Diagnostic Reason Surfaced | Underlying Cause & Resolution |
|---|---|---|
SMTP Authentication Failed (535) |
The email account password or App Password was changed or revoked. Click Fix to re-enter credentials or re-authenticate Google OAuth. | |
| Telegram | 403 Forbidden: bot was blocked by the user |
You may have stopped or blocked the bot in your Telegram app. Open Telegram, find your bot, and send /start. |
Monthly quota reached |
Your plan’s monthly WhatsApp messaging allotment has been reached. Push, Telegram, and Email remain active; upgrade plan or await monthly cycle reset. | |
| Webhooks | HTTP 404 Not Found |
The destination channel or webhook URL was deleted in Slack/Teams/Discord. Generate a new webhook URL and update settings. |
| Push | FCM Device Unregistered |
The companion app was uninstalled or reset on your Android phone. Re-pair the device via QR code under Mobile Alerts. |
Self-Healing & Zero Alert Loss
- Instant Failure Clearing: Successfully sending a test alert (e.g. clicking Send Test Email or Test Webhook) immediately resets the failure counter to zero, clearing the tray tooltip warning without waiting for service cycles.
- SQLite Transactional Outbox: Alerts are written to a local SQLite outbox database before dispatch begins. If your PC loses network access, alerts are not discarded — they are queued and retried automatically with exponential backoff once internet connectivity returns.
- Staleness Diagnostics: If an event is older than the configured drop threshold during an extended offline period, the outbox worker records a detailed diagnostic entry (“Alert dropped: event was X minutes old”) so you have full visibility into dropped events.