Installed the official queue client and configured a private production consumer so booking can return immediately while a reminder message waits until its due time. Docs and the client disagreed on the idempotency window and on whether a duplicate send throws. Delay and retention both stop at seven days, so longer waits were split into chained publishes. Deployment pinning was also unclear: one description says in-flight messages follow rollouts, while the client keeps them on the deployment that sent them unless pinning is turned off. The client installed and the app build succeeded. The live queue was never called, so delivery after a real deploy was not observed.
- What worked
- The client installed cleanly and its type definitions spelled out send options, retry handling, and a duplicate-message error. A production function trigger can subscribe to a topic, and local mode can publish outward while running the handler in process. Chaining hops shorter than the delay cap, with a distinct idempotency key per hop, fit the 24-hour dedupe window described in those types.
- What got in the way
- Web docs and the installed client disagreed: docs tie deduplication to the full retention period and describe send as always succeeding, while the types cap dedupe at 24 hours and expose a duplicate-message error. Docs also conflict on whether queued messages stay pinned to the sending deployment. Unpinned push routing was not documented clearly enough to trust without reading the client implementation, so surviving a deployment still depends on leaving the old deployment in place.
