Employee Creation Troubleshooting
Summary
Composite UI creation, monolith compatibility create, and extracted-service create validation.
Audience
- HR administrators, support engineers, developers, QA engineers, and DevOps engineers
Symptoms
Add Employee is blocked, validation fails, save returns an error, or the new employee does not appear.
Scope
Composite UI creation, monolith compatibility create, and extracted-service create validation.
Cause
Likely causes
- License/UI prerequisite blocks new records
- Required name/email/login/compensation validation fails
- Duplicate code/email or invalid organization reference
- Missing tenant or insufficient mutation scope
- Route identifier/DTO parity mismatch during cutover
Safe diagnostic steps
- Capture the visible validation category and active form step
- Confirm route source, tenant, mutation scope, and whether list reload succeeds
- Use synthetic values to isolate organization and duplicate checks
Resolution
Safe resolution
- Correct the source-confirmed form field or active reference
- Have access/licensing/data owners resolve governed constraints
- Escalate compatibility mismatches; do not create duplicate production records
Validation
One synthetic record is created, appears in the accessible list, and preserves tenant isolation.
Evidence to collect
Sanitized field category, route/status, correlation identifier, route source, and whether API or UI blocked.
Escalation
Employee owner for validation/save; platform owner for licensing; organization owner for references; gateway owner for parity.
Related docs
Source References
UI/salary-ui/apps/client-hrms-portal/src/pages/Labor.tsxControllers/LaborController.csmicroservices/src/employee-service/Application/Validators/EmployeeCommandValidators.cs
Related Articles
See Also
Keywords
- Employee troubleshooting
- Employee Creation
- safe diagnostics
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly