Skip to main content

Performance Notification Troubleshooting

Symptoms​

A lifecycle action succeeds but an expected notification is absent or delivery failed.

Scope​

Performance outbox intent, publication, Notification consumption, intent resolution, duplicate handling, and channel delivery.

Cause​

Likely causes​

Action has no event; outbox not published; consumer unavailable; duplicate/stale outcome; no recipient/template/preference; channel failure.

Safe diagnostic steps​

  1. Confirm the action is one of seven notified contracts.\n2. Check sanitized outbox state and publication category.\n3. Check Notification processed/audit outcome category.\n4. Distinguish intent creation from end-user delivery.

Resolution​

Safe resolution​

Resolve only within the owning boundary using approved support workflows. A successful Performance request should not be repeated merely to force notification.

Validation​

Confirm one processed event identity and the expected Notification outcome category without viewing message content.

Evidence to collect​

Collect only environment category, time window, capability/route, status or error category, sanitized correlation reference, lifecycle state category, and recent approved change context.

Escalation​

Escalate publication to Performance/messaging; resolution/delivery to Notification; audience policy to product/privacy owners.

Source References​

  • microservices/src/performance-service/Infrastructure/PerformanceDbContext.cs
  • microservices/src/notification-service/Application/EventNotificationResolver.cs
  • microservices/src/notification-service/Application/NotificationDispatcher.cs

Summary​

This Draft page provides non-destructive, source-backed diagnosis and explicitly stops where recovery authority is not confirmed.

Audience​

Performance users, support, operations, engineering, QA, architecture, security, and implementation teams.

Overview​

Use supported reads and sanitized evidence. Never expose personal/evaluation content, credentials, configuration values, infrastructure details, or operational commands.

See Also​

Keywords​

  • Performance troubleshooting
  • Safe diagnostics

Revision Information​

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