Leave Request Events

Summary

Successful creation always raises LeaveRequested; initial direct approval also raises LeaveApproved, while Workflow-managed creation stays pending until a later callback.

Audience

Developers, QA, architects, Workflow owners, and support.

Concept

Attendance conflict, missing employee/tenant, invalid dates, approved overlap, or zero calculated units stop creation and produce no request event. Workflow start has no shared Leave-to-Workflow event. A production Workflow start failure can occur after the initial request/outbox commit, so creation failure does not imply the request event was absent.

No request-updated, resubmitted, attachment, or Workflow-started integration contract exists. LeaveRequested has no confirmed consumer. Initial approval and its balance effect can be separate saves/events.

Source References

• microservices/src/leave-service/Domain/Leave/LeaveRequest.cs
• microservices/src/leave-service/Application/LeaveWorkflows.cs
• microservices/src/leave-service/Infrastructure/LeaveDbContext.cs
• microservices/src/leave-service/Application/WorkflowIntegration.cs

Related Articles

• Leave decision events
• Workflow integration events

See Also

• Leave Requests API

Keywords

• LeaveRequested
• Request creation
• Workflow-managed request

Revision Information

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