Attendance Payroll Dependency Operations
Summary
Payroll lock/freeze status protects reopen approval, while Attendance snapshots and Payroll read models follow separate consistency paths.
Audience
- Attendance/Payroll owners, support engineers, QA, architects, and DevOps/SRE
Confirmed dependency behavior
Reopen approval checks whether the affected Payroll period is locked before mutating Attendance. An unavailable or unsuccessful external check prevents safe confirmation and surfaces a dependency failure rather than joining the local database transaction. Snapshot capture stores Attendance-approved period aggregates; Payroll separately consumes Submitted/Approved events into its read model.
For incidents, confirm affected operation, period and tenant safely; check Payroll health/lock response category, Attendance correlation logs, whether Attendance changed, snapshot presence, outbox publication and Payroll consumer ledger/projection. Never bypass a lock through direct data changes.
Escalate to Payroll owner for lock truth, Attendance owner for workflow state, messaging owner for delayed events, and database owner for verified persistence anomalies.
Source References
microservices/src/attendance-service/Infrastructure/PayrollLockClient.csmicroservices/src/attendance-service/Application/Services/ReopenRequestWorkflow.csmicroservices/src/attendance-service/Application/Services/PayrollSnapshotService.csmicroservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
Related Articles
See Also
Keywords
- Attendance operations
- Support
- Reliability
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly