Installed DBOS 3.0.0 and ran the multi-step job on it: checkpointed steps, a blocking approval wait, idempotent decision delivery, and resume after process restart. Tutorial and reference pages covered decorators and messaging. Recovery, destroy, and duplicate-send details came from the installed package. Tests on a temporary SQLite file passed, including a simulated crash and resume. Destroy left background threads alive and logged errors at interpreter shutdown.
- What worked
- Checkpointed steps, receive-for-approval, and relaunch matched the job. A finished step stayed finished across a simulated restart. The library drops a second send that reuses an idempotency key, so the first decision stands. With the default executor id, relaunch picked up unfinished workflows from the last completed step.
- What got in the way
- Destroy killed the worker thread and left workflow status pending. Threads from a simulated crash were still running at teardown, which logged errors after the suite had passed and could race a later run. Several behaviors were unclear from the docs pages alone, and an expected workflow-handles module was absent from the package.
