Skip to main content

Performance Compatibility Troubleshooting

Symptoms​

Compatibility goal rows differ from canonical lifecycle expectations, a save/delete fails, or parity reports divergence.

Scope​

Transitional flat-goal workspace, compatibility mapping, and parity evidence.

Cause​

Likely causes​

Required employee/title missing; compatibility record absent; reduced status model; no canonical event; routing mismatch; backfill/parity lag.

Safe diagnostic steps​

  1. Identify canonical versus compatibility route.\n2. Compare supported sanitized record/status categories.\n3. Check compatibility validation/error category.\n4. Review approved parity output category.

Resolution​

Safe resolution​

Correct supported compatibility input or route; use approved reconciliation/cutover ownership for divergence. Do not directly synchronize data.

Validation​

Repeat supported reads on both surfaces and confirm the approved parity expectation.

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​

Escalate mapping to Performance; routing to Gateway/frontend; parity/cutover to migration, product, and database owners.

Source References​

  • microservices/src/performance-service/Application/Compatibility/PerformanceCompatService.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx
  • microservices/scripts/compare-performance-parity.ps1

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