Skip to main content

Request Lifecycle

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​

Requests can enter directly or through gateway routing. Attendance Service applies correlation, authentication, authorization middleware, tenant-error translation, minimal-API binding, application orchestration, domain validation, persistence, and response adaptation.

Binding and validation​

Minimal APIs bind route integers, query values, and JSON bodies. No separate validator framework was found. Commands and domain aggregates validate business rules. Adapter wrappers translate known result categories and selected exceptions.

Mutation side effects​

Successful writes persist scheduling state and append audit/timeline evidence. Some commands save more than once to obtain generated identifiers or manage the default-policy invariant.

Failure boundary​

Known tenant, domain, argument, validation, not-found, conflict, and forbidden conditions are adapted. Other exceptions are not handled by these wrappers and follow framework/server error behavior.

Source References​

  • microservices/src/gateway-api/Program.cs
  • microservices/src/attendance-service/Program.cs
  • microservices/src/attendance-service/Api/AttendanceDirectEndpoints.cs
  • microservices/src/attendance-service/Application/Services/ShiftPolicyCommands.cs

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