These tasks mix asynchronous delivery, admission control and record identity. You'll decide which boundary owns a retry and which identity makes that retry safe. The new workloads use different arrival rates and failure durations, but the underlying contracts remain the same.
Keep accepted work distinct from completed work. A job ID can be unique while its side effect still repeats, and a queue can preserve order only within the ordering scope you choose. Rate limits must follow the resource being protected, including during a limiter outage. For calculations, use the exact capacity or refill rate given. Leave production headroom as a separate design decision rather than hiding it in arithmetic the prompt did not request.