Skip to main content

LMS Tenant Context Troubleshooting

Symptoms​

Requests return a tenant-context error, expected records are absent, or cross-tenant behavior is suspected.

Scope​

Training tenant resolution, global query filters, tenant assignment, and super-administrator filter behavior.

Cause​

Likely causes​

Missing/invalid tenant context; different client and service tenant categories; super-administrator context; data created under another tenant; or unsupported employee ownership assumptions.

Safe diagnostic steps​

  1. Record the sanitized tenant category used by the client and Gateway.\n2. Confirm the response/error category.\n3. Compare tenant-filtered read behavior with an approved synthetic record.\n4. Do not inspect another tenant's data.

Resolution​

Safe resolution​

Use the approved authenticated tenant flow and retry a supported read. Do not supply arbitrary tenant values or alter stored tenant ownership.

Validation​

Confirm an approved synthetic record is visible only in its expected tenant scope.

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 context propagation to Identity/Gateway; query-filter or ownership concerns to Training and security.

Source References​

  • microservices/src/training-service/Application/Common.cs
  • microservices/src/training-service/Program.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