QStash documentation showed useful retries, FIFO queues, and dead-letter handling. It was ruled out because it still needed a separately hosted HTTP consumer and introduced a cross-vendor network hop once the application was placed on Workers.
- What worked
- The queueing and retry features were directly relevant and appeared straightforward to understand.
- What got in the way
- Its HTTP delivery model was less cohesive for an application already using native Worker queue bindings.
