Skip to main content

LMS Notification Troubleshooting

Symptoms​

A lifecycle change exists but no notification is observed, or a duplicate/failure outcome appears.

Scope​

Training outbox staging, publication boundary, Notification recognition, deduplication, and delivery attempts.

Cause​

Likely causes​

No Training event for the operation; outbox not staged; Training relay not triggered; contract uninvoked; consumer unavailable; duplicate identity; no intent/template/recipient category; delivery failure.

Safe diagnostic steps​

  1. Identify the expected contract name and producer invocation evidence.\n2. Confirm sanitized outbox status category.\n3. Do not infer publication from staging.\n4. Confirm Notification recognition, processed outcome, and delivery category separately.

Resolution​

Safe resolution​

Correct only source-backed producer or consumer defects through normal engineering change. Do not publish, replay, edit ledgers, or retry production delivery from this guide.

Validation​

Use approved synthetic non-production evidence to confirm staging, recognition, deduplication, and delivery categories independently.

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​

Training owns staging; messaging ownership is unconfirmed; Notification owns recognition/delivery; template policy goes to product/Notification.

Source References​

  • microservices/src/notification-service/Messaging/NotificationEventConsumer.cs
  • microservices/src/notification-service/Application/NotificationDispatcher.cs
  • microservices/src/training-service/Infrastructure/TrainingDbContext.cs

Summary​

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

Audience​

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

Overview​

Use supported reads and sanitized evidence. Never expose personal learning data, credentials, configuration values, infrastructure details, or operational commands.

See Also​

Keywords​

  • LMS troubleshooting
  • Safe diagnostics

Revision Information​

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