Notifications or email not delivered

Prerequisites and authority

Start with read-only checks and authorized records. Capture evidence before changes. Stop and escalate when data replacement, financial changes or wider outages are possible.

Notification or email not delivered

Basic

Confirm the business event completed independently. Open in-app history while signed in; do not expect OS/browser push while the app is closed. Check the intended Telegram identity/recipient.

Intermediate

Inspect notification/dispatch records and worker progress. Check provider credentials, network access and recipient state. A blocked bot or absent linkage can affect Telegram delivery without affecting subscription access.

Advanced

Capture dispatch errors and distinguish retries/deduplication from event generation. For SMTP, confirm the release actually supports the configured feature, then inspect connection/authentication versus template/recipient errors.

Use a safe test event after correction. Do not repeatedly trigger paid or disconnection events on real customers. Avoid logging complete credentials or message payloads containing secrets.

Verify in-app storage and each supported external channel separately. Do not invent customer notification preferences as a remedy; they are outside scope. Escalate with event/delivery IDs and timestamps when retry or channel behavior is unclear.