Skip to main content

Employee Search and Listing Troubleshooting

Summary​

UI initial list, local filtering/pagination, monolith access scope, and extracted search differences.

Audience​

  • HR administrators, support engineers, developers, QA engineers, and DevOps engineers

Symptoms​

List fails to load, expected employee is absent, filters show no results, or pagination appears empty.

Scope​

UI initial list, local filtering/pagination, monolith access scope, and extracted search differences.

Cause​

Likely causes​

  • List request failed or access scope excludes the record
  • Active/disabled or organization/employment filter hides it
  • Text search does not match loaded fields
  • Current page is beyond results after state changes
  • Route destination returns a different compatible projection

Safe diagnostic steps​

  1. Clear search/filters and select the correct status segment
  2. Record loaded count and pagination state; reload once
  3. Verify tenant/access scope and route source with an approved read

Resolution​

Safe resolution​

  • Reset filters/page or correct expected status
  • Resolve authentication/access/routing causes through owners
  • Escalate projection mismatch rather than compensating in production data

Validation​

The accessible synthetic record appears under the correct status and filter combination.

Evidence to collect​

Filter values without personal data, count, page, route/status, correlation identifier, route source.

Escalation​

UI owner for local filtering; Employee/access owner for returned scope; gateway owner for parity.

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/pages/Labor.tsx
  • Controllers/LaborController.cs
  • microservices/src/employee-service/Application/Search/EmployeeSearch.cs

See Also​

Keywords​

  • Employee troubleshooting
  • Search and Listing
  • safe diagnostics

Revision Information​

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