I compared task queues with a step workflow for a click that must return immediately and must not repeat a charged create. Search results on whole-handler retry and the day-long name reservation were enough to reject it for this chain. Queue creation was outside this session.
- What worked
- Named tasks, an immediate enqueue, and a queue concurrency cap mapped cleanly onto accepting the click and limiting how many slow runs overlap. The tombstone and at-least-once delivery details were specific enough to decide.
- What got in the way
- The retry unit is the whole handler, so a late failure re-enters earlier successful steps. A task name stays reserved for about a day after deletion, so it cannot unlock a later genuine retry. There is no checkpoint between steps.
