Performance Review Cycle Troubleshooting
Symptoms
Cycle creation/open/close fails, status is unexpected, or a cycle is missing from the workspace.
Scope
Canonical review-cycle UI, commands, domain state rules, and persistence.
Cause
Likely causes
Required field/date validation; invalid date order; name length; attempting to open a non-draft or reopen/close an invalid state; tenant mismatch.
Safe diagnostic steps
- Record requested action and current status category.\n2. Check the UI error and supported cycle read.\n3. Verify required fields and date ordering without capturing notes.\n4. Check audit/timeline evidence category.
Resolution
Safe resolution
Correct input or perform only a state transition allowed by the documented lifecycle. Do not edit stored status.
Validation
Reload cycles and confirm expected status plus audit/timeline evidence.
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 inconsistent state/evidence to Performance; persistence anomalies to database owner.
Related documentation
Source References
microservices/src/performance-service/Domain/ReviewCycle/ReviewCycle.csmicroservices/src/performance-service/Application/Commands/ReviewCycleCommands.csUI/salary-ui/apps/client-hrms-portal/src/pages/hr/TalentAdminPages.tsx
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.
Related Articles
See Also
Keywords
- Performance troubleshooting
- Safe diagnostics
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly