K
M
MM
E
J
J
# Beta. Queue backlog data with adaptive sampling. Queues that are not being written to, or read from, will not return data, even if they have a backlog.E
EJJ
queue handlers have exactly the same limits (cpu time etc) as a fetch
env.YOUR_BINDING_NAME.send() (and passing in envObject.keys(env) and paste the output? DM me if you prefer.MMMMM
MM
E
batch object to know which Queue you're consuming from in that particular execution.EWorkers > Overview > (your worker) > Triggers > Queues (bottom of page)) or by removing it from the wrangler.toml.ack() on every message (or the entire batch) when handling it? .retry() would exist for the cases where you want to explicitly, negatively acknowledge.
this post; if no, reply with why! Keep in mind I am familiar with other messaging systems; there’s not an agreed-upon approach here!MMM
YOUR_QUEUE.send(). In the longer term we’re exploring other on-ramps to support this nativelyMM
U
# Beta. Queue backlog data with adaptive sampling. Queues that are not being written to, or read from, will not return data, even if they have a backlog.queueenv.YOUR_BINDING_NAME.send()Object.keys(env)batchWorkers > Overview > (your worker) > Triggers > Queues (bottom of page).ack().retry()YOUR_QUEUE.send()export default {
...
async queue(batch: MessageBatch, env: Env, ctx: ExecutionContext) {
if (batch.queue === 'my-first-queue') {
doSomething()
} else if (batch.queue === 'my-other-queue' {
doSomethingElse()
}
...
},
};