ReadonlywebhookReadonlyworkerOptionaltokens: string[]Optionaltoken: stringOptionallifo: booleanOptionalstate: stringOptionallimit: numberOptionalkeepLogs: numberOptionaltoken: stringOptionalerror: stringOptionaltoken: stringOptionalstack: string[]OptionalremoveOnFail: booleanDrop the retained result of a job removed on completion (removedResults). The
Cancel outcome (cancelWithOutcome) calls it when it reports the job missing, so an
ACK that removed the job between the refusal and the state read leaves no result.
The completion lookup (WaitJob, the embedded wait reader): distinguishes a completed
generation from a valid undefined result, including cold SQLite completions. A job
removed on completion answers from its retained result (removedResults, memory
only, short-lived) while no current generation holds the ID.
Optionalcount: numberOptionalmaxJobs: numberOptionalmaxJobs: numberAsync result port used by transports (GetResult); memory and SQLite remain synchronous internally. It reads completed jobs only, as before: the retained result of a job removed on completion answers the completion lookup, not GetResult.
Optionaltoken: stringOptionaltokens: string[]Optionaltoken: stringOptionaltoken: stringOptionaltoken: stringOptionalcount: numberOptionalsignal: AbortSignalOptionalgroupOptions: GroupPullOptionsOptionalsignal: AbortSignalOptionalgroupOptions: GroupPullOptionsOptionalconcurrency: numberOptionaloptions: CreateWorkerOptionsOptionaltoken: stringRemove one terminal DLQ job without re-enqueuing it.
OptionalnewTtl: numberOptionaljobId: JobIdOptionallimit: numberOptionaldurationMs: numberOptionalttlMs: numberOptionalmessage: stringOptionalsignal: AbortSignalwaitForJobCompletion that also returns the job's result. A wait woken by the
job's completed event answers with the event's data, the worker's return value,
so a job removed on completion (which keeps no result) still returns it to a
waiter registered when it completed. A wait released without an event reads the
store only while its completion is cached; shutdown clears that cache before the
callback runs. result is undefined on a timeout or abort. An invalid timeoutMs
throws synchronously, as waitForJobCompletion does.
Optionalsignal: AbortSignal
Non-throwing flush that respects a scheduled write retry backoff.