I installed the queue SDK and used its types to publish one message after a checkout webhook is verified, with the payment event id as the publish idempotency key. A consumer sends the confirmation under a concurrency cap, retry delay, and delivery limit set as a beta queue trigger. The production build included that consumer. Publishing was not run locally because that needs platform credentials.
- What worked
- The package installed on the first attempt, and the type declarations covered send, consumer callbacks, retries, and message metadata. Idempotent publish plus a separate consumer matched the need to acknowledge the payment webhook immediately and retry mail after bursts, timeouts, and crashes.
- What got in the way
- The concurrency setting was absent from the main concepts table and showed up on a beta trigger example, so the project configuration was hard to confirm. The SDK layout was unclear until the installed declarations were opened. Delivery, backoff, and deduplication were never observed against the hosted queue.
