Skip to main content

LMS Troubleshooting Documentation

Summary​

Safe diagnosis is organized by authentication, tenant context, lifecycle area, dependencies, outbox, migrations, and a decision tree.

Audience​

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

Overview​

Use supported read paths, current status categories, sanitized correlation references, and synthetic reproduction. Do not use direct data changes, production commands, payload inspection, replay, or destructive migration actions.

Diagnostic principles​

  • Separate client navigation visibility from backend authorization.
  • Confirm tenant context before diagnosing missing data.
  • Compare the requested action with the current lifecycle state.
  • Separate Training persistence from Document, Gateway, messaging, and Notification outcomes.
  • Treat outbox staging and downstream delivery as distinct states.
  • Escalate when recovery authority, ownership, or policy is not source-backed.

Documentation map​

Requires confirmation​

Production recovery authority, severity policy, response objectives, escalation contacts, and approved evidence-retention policy require confirmation.

Source References​

  • microservices/src/training-service/Application/Common.cs
  • microservices/src/training-service/Program.cs
  • microservices/src/training-service/Api/TrainingEndpoints.cs
  • microservices/src/training-service/Domain/TrainingEntities.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/TalentAdminPages.tsx
  • microservices/src/training-service/Application/DocumentServiceClient.cs
  • microservices/src/gateway-api/EssEndpoints.cs
  • UI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsx
  • microservices/src/training-service/Infrastructure/Persistence.cs
  • microservices/src/shared-kernel/Messaging/OutboxProcessor.cs

See Also​

Keywords​

  • LMS troubleshooting
  • Safe diagnostics

Revision Information​

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