Skip to main content

Expense Notification Delivery Troubleshooting

Summary​

No notification appears after approval, rejection, or Paid; a channel is missing; or duplicate/stale handling is observed.

Audience​

  • Employees, managers, HR administrators, support engineers, developers, QA engineers, DevOps engineers, and solution architects, as applicable to the symptom.

Cause​

Use the verified possibilities in Likely causes; do not infer an environment-specific cause without evidence.

Resolution​

Use Safe resolution, then complete Validation. Stop and escalate if the required action exceeds approved access.

Symptoms​

No notification appears after approval, rejection, or Paid; a channel is missing; or duplicate/stale handling is observed.

Scope​

Expense publication, Notification consumption, intent resolution, idempotency, recipient/template/channel, and delivery.

Likely causes​

  • Expense event pending/failed
  • Notification consumer delay/failure
  • Duplicate or stale event skipped
  • Recipient or template resolution did not produce delivery
  • Claimant email not enriched
  • Channel delivery failure

Safe diagnostic steps​

  • Confirm claim transition and Expense outbox state
  • Check Notification processed-event outcome
  • Check resolver/message evidence through supported Notification surfaces
  • Separate in-app intent from external channel delivery
  • Do not include recipient address or message content in tickets

Safe resolution​

Allow supported retry at the owning layer or correct authoritative recipient/template configuration through its owner. Expense cannot resend a notification directly.

Validation​

Expected Notification processing and channel state are recorded once for the event identity.

Evidence to collect​

Event type/identity, publication state, consumer outcome, intent/message/channel status category, timestamp/correlation; no recipient/customer content.

Escalation​

Messaging owner if unpublished/delayed; Notification owner for intent/delivery; Identity/Employee owner for recipient enrichment.

Requires confirmation​

Any corrective action beyond the supported resolution, incident ownership, response objectives, and production evidence locations require confirmation.

Source References​

  • microservices/src/notification-service/Messaging/NotificationEventConsumer.cs
  • microservices/src/notification-service/Application/EventNotificationResolver.cs
  • microservices/src/notification-service/Application/NotificationDispatcher.cs

See Also​

Keywords​

  • Expense troubleshooting
  • Notification Delivery

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-16
  • Review cycle: Quarterly