Not without using something like Durable Objects where the Workers can read/write state for the othe
Not without using something like Durable Objects where the Workers can read/write state for the other
batch.messages, whether it's a batch or 1 or 100.

queue handler throws an exception, otherwise returning without an error is considered success.
ackAll() as described there too 
k items every n seconds within a given topic. DOs satisfy this use case for now though 

await env.MY_QUEUE.send(msg, { deliveryDelay: 600 }) on the producer side, and retry delays on the consumer side - e.g. messages.batch.retryAfter(300) or .retryAfter(seconds: number) on a per-message basis. API not final.33ba9f42ca7b9084cf895328953209aae9da953df1a8d8f32f3832fe56env.DO.idFromString() to transform to a DO idenv.DO.idFromString()