Installed the workflow package and used it so class cancellations, reminders, and a one-at-a-time waitlist could outlive a single serverless request. Each send is its own step, sleep covers the one-hour offer, and a hook resumes the run when someone answers. The package installed cleanly and two production builds compiled the workflows. Live runs were not executed.
- What worked
- Pricing and concept docs matched the constraints: a run can sleep for an hour without holding a function open, a hook can race an answer against that deadline, and a failed send retries only that step. An in-progress hour stays within the included plan because the short retention window applies after the run finishes. Both production builds reported the workflows compiled.
- What got in the way
- Guidance was split across the host docs, the SDK docs site, and markdown inside the installed package. A timeouts cookbook file was missing from the package. Sleep, start, run cancellation, and error types were scattered through declaration files and took repeated lookups. A cookbook constructed dates inside a workflow, which fights replay, so a memoized step had to supply a stable timestamp. The project language target has no explicit resource-disposal syntax, so hook cleanup was written by hand. Try and catch versus suspension needed a second read of the foundations docs before it was safe to keep.
