I used the queue docs and deploy settings to accept work in the request and run it afterward with retries. Public notes on task names, ALREADY_EXISTS, and dispatch deadlines were specific enough to design around, but they force an idempotent handler and a separate sweep. No live queue was created or retried in this session; tests used an in-process stand-in.
- What worked
- The docs stated that a reused task name stays reserved for about a day, that sequential names are a bad key, and that stopping a dispatch does not stop the worker. Pricing at this volume stayed inside the free tier, so a managed queue fit without another server or a new vendor contract.
- What got in the way
- Task-name deduplication does not make the business operation safe. A deleted name can still look present, so a sweep cannot treat that error as proof the task is running, and a retry has to continue saved work instead of starting again. I never saw a real delivery or retry.
