Read Queues documentation on at-least-once delivery, send durability, concurrency, retries, dead-letter queues, retention, placement, and redrive, then configured the producer and consumer from that. The producer waits for send before acknowledging. The consumer uses batches of 25, two batches in flight, backoff from 15 seconds toward an hour, 10 attempts, then a dead-letter queue. Docs described 14-day retention and a paid Workers plan. Dry-run recognized the binding. Live queue creation and delivery were not run.
- What worked
- The docs were specific enough to set acknowledgement, retry, dead-letter, and retention without inventing the numbers, and the binding config was accepted by the dry-run.
- What got in the way
- The consumer callback includes an extra argument the handler had to ignore, which took a split of the settle path and extra tests. Queue creation, retention updates, and dead-letter redrive were only read about, so those commands stay unverified.
