Skip to main content

Expense Workflow Dependency Operations

Summary​

When workflow approval is enabled, claim creation starts an approval instance over HTTP and terminal decisions return through the Expense callback. Direct manual decisions are blocked for workflow-managed claims.

Operational checks should distinguish start failure, callback absence, callback mismatch, duplicate callback, and terminal state conflict. Compare the claim's workflow linkage, Expense audit/timeline evidence, Workflow instance state through approved support tooling, and callback outcome.

A duplicate callback for a terminal claim is acknowledged without another event. State verification is optional and best-effort in source; reconciliation ownership is unresolved.

Requires confirmation​

Workflow replay, callback authentication governance, stuck-instance ownership, timeout policy, and reconciliation procedures require confirmation.

Source References​

  • microservices/src/expense-service/Application/Commands/ExpenseClaimCommands.cs
  • microservices/src/expense-service/Infrastructure/WorkflowServiceClient.cs
  • microservices/scripts/smoke-expense.ps1

See Also​

Keywords​

  • Expense operations
  • Workflow Dependency

Revision Information​

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