Chose this as the off-host queue so jobs survive replacing web and worker machines. Documented provisioning via the platform Redis extension and a secret URL. Never created an account or opened a production database; local Redis stood in.
- What worked
- The intended production shape was easy to describe: a secret URL, TLS-capable client, queue and worker names in checked-in config, and no volume on the worker machine.
- What got in the way
- No live instance was provisioned, so retry durability, TLS, and extension-create behavior were not observed. Runtime still depends on an operator setting the secret after deploy config is applied.
