Retry Handling
Business Purpose
Recover from transient channel failures while retaining an evidence trail and a controlled manual recovery path.
Actors
Channel providers, automated dispatch, support operators, notification administrators and recipients.
Business Flow
Automatic delivery uses a bounded, configurable exponential retry policy. Every try creates a delivery-attempt record. The first success marks the message sent; exhausting attempts marks it failed. An operator can request manual retry, which clears the prior error, returns the message to pending and runs the same delivery loop.
Responsibilities
Support checks recipient data, template state and provider readiness before manual retry. Service owners tune bounded retry behavior. Product owners define escalation and customer communication for persistent failures.
Business Rules
Retry applies to an existing message and does not rerender its stored content. A missing sender is a failure. A manual retry is successful only when the message becomes sent; otherwise the operation reports a conflict rather than masking continued failure.
Integrations
Retry uses the original message, channel registry, sender, delivery-attempt store, audit trail and telemetry. The operations UI exposes retry for failed records.
Limitations
No dead-letter business workflow, bulk retry approval, alternate channel or automated operator escalation was found. Repeated attempts can resend if a provider accepted a request but returned an ambiguous failure.
Requires Confirmation
Confirm retry limits per provider, safe retry windows, idempotency expectations at providers, bulk recovery procedures and escalation ownership.
Source References
microservices/src/notification-service/Application/RetryPolicy.csmicroservices/src/notification-service/Application/NotificationDispatcher.csmicroservices/src/notification-service/Api/NotificationEndpoints.csUI/salary-ui/apps/client-hrms-portal/src/pages/admin/NotificationCenterAdminPage.tsx
Related Articles
See Also
Keywords
Retry, attempt, transient failure, manual recovery.
Revision Information
Draft; reviewed 2026-07-21; next quarterly review 2026-10-21.