Coordinate a workflow
Make dependencies, ownership and recovery understandable.
What to have ready
- Requested business result/application, step dependencies/consent/ownership/compensation rules and versioned service/storage contracts.
When you run it
- Working code checks need project runtime/persistence; restart claims need reopened state/fresh processes, concurrency claims actual competing workers.
A task to start with
Coordinate several business steps through partial failure.
An illustrative request
Use the workflow-coordination guidance with the versioned operation contracts, dependencies and business policy. Define success, uncertain completion, recovery and permitted compensation from actual authority.
How to check the result
Exercise relevant success, rejection and recovery paths in an isolated system; inspect persisted progress where the contract requires it.
This preview explains the task and checking approach. It is not a demonstrated customer outcome or a guarantee.
See what a useful orientation looks like.
The free worked example includes source files, an actual entry-point trace and executed checks you can compare with the code.
Open the worked example