Skip to main content

Leave Attendance Dependency Operations

Summary​

Leave consults Attendance for conflict checks on confirmed creation and approval paths; calendar ownership remains transitional.

Audience​

Support, DevOps/SRE, Leave and Attendance owners, QA, and architects.

Overview​

Investigate by confirming tenant/employee/date context without exposing personal data, reviewing safe correlation traces for the dependency call, and comparing the resulting conflict category with approved business evidence. Do not modify Attendance or Leave data to bypass a conflict.

Dependency failure behavior must be taken from the exact call path and environment; broad fail-open/fail-closed claims are Requires confirmation. Holiday and weekly-off ownership overlaps with Attendance and legacy payroll-oriented configuration, so calendar precedence also requires confirmation.

Escalate confirmed conflicts to the business owner, dependency failures to Attendance and Leave owners, and routing/authentication failures to platform owners.

Source References​

  • microservices/src/leave-service/Infrastructure/AttendanceServiceConflictClient.cs
  • microservices/src/leave-service/Application/LeaveWorkflows.cs
  • microservices/src/attendance-service/Application/Services/AttendanceQueries.cs

See Also​

Keywords​

  • Leave operations
  • Leave Attendance Dependency Operations
  • Service support

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-15
  • Review cycle: Quarterly