Skip to main content

Tenant and Employee Context

Summary​

Records do not load, capture fails, or self-service cannot resolve an employee.

Audience​

Employees or administrators affected by the scenario, first-line support, QA, service owners, and operations.

Symptoms​

  • Records do not load, capture fails, or self-service cannot resolve an employee.

Scope​

Tenant and employee context resolution.

Likely causes​

Missing tenant, missing employee profile, inactive profile, pre-joining date, or employee outside authorized scope.

Cause​

The confirmed cause categories are listed under Likely causes above; determine the applicable category from sanitized evidence before taking action.

Safe diagnostic steps​

  1. Confirm the selected tenant, authenticated employee mapping, target date, active profile status, and authorized self/team/all scope through approved screens/logs.
  2. Preserve tenant isolation and redact personal or security-sensitive data.
  3. Do not use direct database changes, authorization bypasses, or ad hoc broker operations.

Safe resolution​

Correct the tenant selection or employee master/profile data through its owning workflow; request access correction when scope is wrong.

Resolution​

Apply only the Safe resolution described above and remain within the documented ownership boundary.

Validation​

Reload the same date and verify a tenant-scoped, authorized result.

Evidence to collect​

Sanitized employee reference, date, tenant reference, route, response category, correlation identifier.

Escalation​

Employee/Identity owner for mapping; Attendance owner for a confirmed valid context failure.

Source References​

  • microservices/src/attendance-service/Application/Services/AttendanceCommands.cs
  • Controllers/AttendanceController.cs

See Also​

Keywords​

  • Attendance
  • Troubleshooting
  • Tenant and Employee Context

Revision Information​

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