Error Handling
Audience
Developers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.
Reference Content
This page records source-verified Workforce Scheduling API behavior and boundaries.
Summary
Application commands return typed results for validation, missing resources, conflicts, and forbidden operations. Endpoint adapters map those results differently for native and compatibility clients.
| Condition | Native mapping | Compatibility mapping |
|---|---|---|
| Success | 200 standard envelope | 200 bare value |
| Validation | 400 standard error envelope | 400 bare error |
| Not found | 404 standard error envelope | 404 bare error |
| Conflict | 409 standard error envelope | 400 bare error |
| Forbidden | 403 standard error envelope | 403 bare error |
| Missing tenant exception | 400 tenant error envelope | 400 bare error |
| Domain/argument exception | 400 standard error envelope | 400 bare error for handled argument cases |
Compatibility delete has a special plain-text success. Framework binding failures follow minimal-API behavior and are not explicitly reshaped in these adapters.
Unhandled failures
The wrappers do not define a general exception response. Unexpected exceptions therefore follow framework/server handling. No module-specific problem-details contract, centralized exception handler, retry contract, or error-code catalog was verified.
Information exposure
Several source errors include submitted identifiers or names. Production error-detail policy requires security review.
Source References
microservices/src/attendance-service/Application/Common/Cqrs.csmicroservices/src/attendance-service/Api/AttendanceDirectEndpoints.csmicroservices/src/attendance-service/Api/AttendanceCompatibilityEndpoints.csmicroservices/src/attendance-service/Program.cs
Related Articles
See Also
Keywords
- Workforce Scheduling API
- Shift endpoints
- Attendance policy API
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20