Read the queues concepts, quickstart, and background-jobs guide to choose one production system. The docs name Queues as the shared backend and a functions runtime as the consumer, and they point this storefront shape at the workflow layer. No queue was created and the live service was not called.
- What worked
- Concepts and the quickstart were enough to name a managed queue and the worker that consumes it, and to compare that model with workflows. The background-jobs guide gave a direct recommendation for this kind of app.
- What got in the way
- Idempotency, progress, and terminal failure still needed extra searches across the queues pages and the workflow docs. The recommended programming interface is a different product, so a queues-only setup was not fully specified from these pages.
