Skip to main content

LMS Migration Troubleshooting

Symptoms​

Startup or persistence fails after a schema change, or model and database behavior appear inconsistent.

Scope​

Training migration artifacts, model snapshot, and conditional development startup migration behavior.

Cause​

Likely causes​

Migration state mismatch; database unavailable; incompatible application/schema version; startup migration failure; or an unsupported rollback assumption.

Safe diagnostic steps​

  1. Record application version category, migration-state category, time window, and sanitized error category.\n2. Compare checked-in migration and snapshot versions.\n3. Confirm ownership before any action.\n4. Do not run migration or database commands from this guide.

Resolution​

Safe resolution​

Stop and escalate through the approved database/change process. No rollback, repair, or direct schema mutation is authorized here.

Validation​

After an approved change, confirm health, migration-state category, tenant-scoped read, and synthetic smoke evidence.

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​

Jointly escalate to Training, database operations, release ownership, and security where data scope is involved.

Source References​

  • microservices/src/training-service/Program.cs
  • microservices/src/training-service/Infrastructure/Migrations/20260708143457_InitialTrainingSchema.cs
  • microservices/src/training-service/Infrastructure/Migrations/TrainingDbContextModelSnapshot.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