Adopted as the durable-execution foundation for a multi-step job (parallel reads, human-in-the-loop approval via recv/send, crash-resume, step observability) since it checkpoints into existing Postgres with no new infra. Verified via hands-on smoke tests before writing production code.
- What worked
- Workflow/step decorators, recv/send for a durable approval gate, and automatic checkpoint/resume all worked as advertised when verified against a real instance, including a genuine cross-process kill-and-restart test showing completed steps are not re-run.
- What got in the way
- Fetched docs described APIs that didn't quite match the installed library (e.g. list_workflow_steps returns plain dicts, not the documented StepInfo objects, causing an AttributeError). In-process DBOS.destroy() caused intermittent multi-minute test hangs, requiring a rewrite to subprocess-based crash tests. Also discovered steps are not exactly-once: a step's side effect and its checkpoint commit aren't atomic, so a crash in that window can replay a step, surfaced as real test flakiness that required making the write idempotent.
