Skip to main content

Workflow API Request Lifecycle

Summary​

Native requests pass correlation, authentication and authorization middleware before Minimal API binding. Mutation handlers then execute application/domain behavior and save through one DbContext boundary.

Sequence​

Query distinction​

Queries normally use no-tracking reads and do not save or generate outbox messages. Definition detail uses a repository-backed loader.

Error path​

Typed command failures are translated centrally. Tenant-related context exceptions are translated by middleware. Other unhandled failures use framework behavior.

Requires Confirmation​

External gateway stages, transaction retries, standardized exception handling and end-to-end correlation require confirmation.

Source References​

  • microservices/src/workflow-service/Program.cs
  • microservices/src/workflow-service/Api/WorkflowEndpoints.cs
  • microservices/src/workflow-service/Application/Commands/WorkflowInstanceCommands.cs
  • microservices/src/workflow-service/Infrastructure/WorkflowDbContext.cs
  • microservices/src/workflow-service/Api/EndpointResults.cs

See Also​

Keywords​

Workflow API, approval endpoint, Workflow Service.

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20