Skip to main content

Performance Tenant Context Troubleshooting

Symptoms​

A request reports missing tenant context, returns no expected rows, or appears under the wrong tenant scope.

Scope​

Tenant extraction, query filters, audit/timeline/outbox context, and compatibility requests.

Cause​

Likely causes​

Missing/invalid tenant claim/header context; session tenant mismatch; unsupported direct call; stale client tenant selection.

Safe diagnostic steps​

  1. Confirm the active tenant category in the portal.\n2. Confirm the request used the supported gateway/client path.\n3. Compare sanitized tenant context category across request, audit, and expected read.\n4. Stop immediately on suspected cross-tenant evidence.

Resolution​

Safe resolution​

Re-establish the approved tenant session or correct upstream context through the owning Identity/Gateway process. Never rewrite tenant data.

Validation​

Repeat a supported tenant-scoped read and confirm only expected scoped rows appear.

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​

Suspected cross-tenant behavior requires immediate Performance, security, Identity, and database-owner escalation.

Source References​

  • microservices/src/performance-service/Application/Common/Abstractions.cs
  • microservices/src/performance-service/Program.cs
  • microservices/src/performance-service/Infrastructure/PerformanceDbContext.cs

Summary​

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

Audience​

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

Overview​

Use supported reads and sanitized evidence. Never expose personal/evaluation content, credentials, configuration values, infrastructure details, or operational commands.

See Also​

Keywords​

  • Performance troubleshooting
  • Safe diagnostics

Revision Information​

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