Skip to main content

LMS Course Troubleshooting

Symptoms​

Course create, publish, archive, list, or assignment preparation fails or a course is missing.

Scope​

Course admin UI and backend course lifecycle.

Cause​

Likely causes​

Missing required code/title; code length or tenant uniqueness conflict; missing record; invalid lifecycle assumption; load failure; or absent dedicated editor/content UI.

Safe diagnostic steps​

  1. Confirm operation and current course status category.\n2. Confirm required field presence without collecting content.\n3. Check whether the failure is UI validation, backend validation, conflict, or not-found.\n4. Confirm the user is on the native admin workspace.

Resolution​

Safe resolution​

Correct only supported input and use publish/archive actions consistent with current state. Use APIs only through approved clients. Do not directly alter course records.

Validation​

Reload the course table and confirm status plus expected audit/timeline category.

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​

Validation/lifecycle defects go to Training; missing editor/filter behavior to frontend/product; tenant conflicts to Training/security.

Source References​

  • 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

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