Chose this as the orchestration layer for fan-out notification sends and a one-hour-per-offer waiting queue, because durable sleep plus step retries removed the need to hand-roll a cron state machine on a serverless host. Installed the SDK, wrote three workflows and several step modules, wrapped the framework config with its plugin, and confirmed the production build emitted the generated workflow routes.
- What worked
- The core primitives map directly onto the problem: durable steps for each send, duration-string sleeps for the hold timer, and a plugin that compiles everything into routes with no extra infrastructure. Getting-started and framework-specific pages were enough to wire it up correctly on the first try, and the shipped type definitions were readable enough to confirm the real API surface.
- What got in the way
- Documentation did not cover whether a wait-for-external-event handle can carry a timeout, so I had to read the bundled declaration files to learn the options type has no such field. Replay semantics for racing an event wait against a timer were also undocumented, so I avoided that pattern and used sleep-then-recheck instead. A short page on determinism and replay guarantees would have saved a lot of verification.
