awaitly-patterns

Typed async workflows use step-based composition with run() and createWorkflow(deps) to automatically infer and normalize errors across multi-step processes. This replaces brittle try/catch logic by requiring dependencies to return AsyncResult values for static analysis.

Automatic error inference normalizes errors across workflow steps by requiring dependencies to return AsyncResult values. Using run and createWorkflow patterns ensures errors propagate predictably across multi-step async processes without manual try/catch blocks.

Async workflows support retries, timeouts, and boundary error handling through dependency injection. Pass dependencies returning AsyncResult values into createWorkflow(deps), then configure retry and timeout logic within the step composition using the run pattern.

Testing async workflows supports per-item steps, loops, and concurrency patterns. Static analysis tooling validates typed errors during testing, ensuring your async workflow logic handles concurrent operations and boundary errors correctly across multi-step processes.

createWorkflow(deps) applies dependency injection to endpoint boundary error handling by passing dependencies that return AsyncResult values. This pattern ensures automatic error inference and normalization across endpoint boundaries in DI-heavy applications.