Direct Asynchronous Code Issuance

Context

A request can generate up to five thousand codes. Work must retain progress and avoid exceeding the requested count across restarts.

Decision

Saved code batches invoke the module’s worker asynchronously and resume from stored progress without a separate queue or data-job dispatcher.

Alternatives Considered

Dispatch code generation through import data jobs. The implemented data-job mechanism organizes imported records rather than a bounded code generator.

Always create the whole batch inside the interactive request. The deployed path uses background execution; inline execution is retained when no worker is configured.

Consequences

Recovery can use failed Lambda execution, repeated requests or stale progress reads. Without a supplied request key, a repeated request can create another batch.