Skip to main content

Workflow Rejection Events

Summary​

One successful rejection queues two events: task rejection first, then instance rejection.

Event pair​

The task event includes task/stage/actor/reason. The instance event includes instance/key/subject/actor/reason. Both map to schema-version-1 integration contracts and are persisted during the same save.

Persistence state​

The instance becomes terminal Rejected. Sibling Pending tasks are not changed and emit no event.

Downstream status​

No verified consumer applies the terminal event to source-module records. Callback receivers exist, but Workflow does not invoke them.

Requires Confirmation​

Consumer choice between task and instance rejection, sibling-task cleanup and callback dispatch require confirmation.

Source References​

  • microservices/src/workflow-service/Application/Commands/WorkflowInstanceCommands.cs
  • microservices/src/workflow-service/Domain/Workflow/WorkflowInstance.cs
  • microservices/src/workflow-service/Infrastructure/WorkflowDbContext.cs

See Also​

Keywords​

Workflow events, integration contracts, transactional outbox.

Revision Information​

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