Skip to main content

Tenant and User Context Troubleshooting

Symptoms​

Requests fail for missing tenant/actor context or return an unexpected tenant-scoped result.

Scope​

Recruitment tenant context, actor extraction, query filters, and UI tenant user context.

Cause​

Likely causes​

  • Tenant header/claim context is missing.
  • Authenticated portal context and service context disagree.
  • Actor is required for the command but absent.
  • Gateway forwarding or token claims require confirmation.

Safe diagnostic steps​

  1. Verify the request used an approved tenant entry flow.
  2. Confirm a tenant context is present without recording its sensitive token.
  3. Compare a supported tenant-safe read with the failing operation.
  4. Trace the safe correlation reference across gateway and service.

Resolution​

Safe resolution​

Correct context through approved authentication/gateway configuration owners; do not inject headers manually in production or change stored records.

Validation​

Repeat an approved read and the original non-destructive scenario under the correct tenant.

Evidence to collect​

Collect the time window, environment category, affected operation, expected/actual status category, safe record reference, correlation reference where available, dependency/error category, and recent approved change. Exclude personal data, resumes/documents, interview notes, tokens, offer/compensation values, credentials, bank/KYC data, secrets, and configuration values.

Escalation​

Escalate to Identity/security, Gateway, and Recruitment service owners; involve privacy/security for suspected cross-tenant exposure.

Source References​

  • microservices/src/recruitment-service/Program.cs
  • microservices/src/recruitment-service/Infrastructure/Gateways.cs
  • microservices/src/recruitment-service/Application/Common/Abstractions.cs

Summary​

This Draft page summarizes source-backed Recruitment behavior and explicitly marks incomplete governance or implementation.

Audience​

Recruitment stakeholders, product, engineering, QA, support, operations, architecture, security, and implementation partners as applicable to this page.

Overview​

Use the source-backed sections above as the authoritative scope. Unsupported behavior remains Requires confirmation or Not implemented.

See Also​

Keywords​

  • Recruitment
  • Hiring lifecycle
  • Draft documentation

Revision Information​

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