Installed the Python package at 2.31.1 and used it as the shared engine for a multi-step job: parallel reads as child workflows, a blocking receive as the approval gate, recorded steps, and recovery after restart. Testing, workflow, and configuration docs were enough to draft that design. A linked recovery test was missing, and cancel, receive, executor identity, and the status written on recovery were confirmed in the installed source. Pause, resume, failing-step, and model-swap tests then passed.
- What worked
- Child workflows kept parallel reads ordered across recovery, step history included errors, and a restarted process skipped finished steps and performed the write once. Tests ran on the in-process SQLite system database. Named steps, retries, a configurable notification poll interval, and a stable executor id were available without a separate conductor service.
- What got in the way
- No pause operation is exposed. Cancel does not wake a thread blocked in receive, and a second execution that reaches the same receive conflicts with the leftover waiter. Recovery queued the run as enqueued, which the first approval check rejected. The default executor id stays on the original machine, so another replica will not claim a crashed run unless that id is fixed and a single process is used. A long receive and non-daemon threads kept the test process alive until paused runs were given a decision.
