Leave Workflow Dependency Operations

Summary

Leave can use direct decisions or optional Workflow delegation; operators must distinguish these modes before diagnosing a stuck request.

Audience

Support, DevOps/SRE, Leave and Workflow developers, QA, and architects.

Overview

When Workflow is disabled, confirmed decision paths apply directly. When enabled, Leave starts a workflow and records correlation/state for later callback handling. Start or callback failures can leave a request requiring reconciliation.

For safe validation, confirm the configured mode without exposing values, correlate the Leave request with approved Workflow evidence, compare current Leave and Workflow states, and review safe logs/traces. Duplicate callbacks are expected to meet source-defined state/idempotency handling; do not replay callbacks manually.

Escalate start failures to Leave and Workflow owners, routing/authentication issues to platform/identity owners, and state divergence to both product owners. Callback trust mechanics are intentionally excluded.

Source References

• microservices/src/leave-service/Application/WorkflowIntegration.cs
• microservices/src/leave-service/Infrastructure/WorkflowServiceClient.cs
• microservices/src/leave-service/Api/LeaveEndpoints.cs

Related Articles

• Leave Operations
• Leave technical documentation

See Also

• Leave events
• Leave troubleshooting

Keywords

• Leave operations
• Leave Workflow Dependency Operations
• Service support

Revision Information

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