Skip to main content

Employee Troubleshooting Decision Tree

Summary​

Access, list/search, create/update, assignments, timeline, event delivery, database/migrations, and gateway compatibility.

Audience​

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

Symptoms​

Use when the initial Employee symptom has not yet been assigned to a responsible layer.

Scope​

Access, list/search, create/update, assignments, timeline, event delivery, database/migrations, and gateway compatibility.

Cause​

Likely causes​

  • The failing layer has not yet been identified
  • Multiple transitional boundaries can produce similar user-visible symptoms

Safe diagnostic steps​

  1. Follow the Mermaid tree from the reported symptom
  2. Record route source, safe status category, tenant scope, and correlation identifier before escalation

Decision tree​

Resolution​

Safe resolution​

  • Open the linked topic and follow only its safe resolution
  • Stop and escalate when ownership, data repair, replay, routing, or security approval is required

Validation​

The issue is assigned to one primary topic/owner with a minimal reproducible synthetic check.

Evidence to collect​

Selected branch, time, scope, route source, status, correlation identifier, and recent change.

Escalation​

Use Support and Escalation when the branch crosses ownership or sensitive-data/security boundaries.

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/App.tsx
  • microservices/src/employee-service/Program.cs
  • microservices/src/gateway-api/Program.cs
  • microservices/src/shared-kernel/Messaging/OutboxProcessor.cs

See Also​

Keywords​

  • Employee troubleshooting
  • Decision Tree
  • safe diagnostics

Revision Information​

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