CD
Cloudflare Developers•2mo ago
Mitya

Several questions about developing locally with queues

1. The Get started guide for queues suggests running wrangler tail to watch published messages arrive. However this gives an error 10007 when working locally. Should this command work locally? 2. How does one configure the batch size/frequency of a queue when working locally, since the queue is automatically-created by Wrangler? That is, you don't run the create command when working locally, nor do you bind the queue explicitly to your config TOML/JSON. 3. In my consumer handler, I have: 
async queue(batch, env) {
    for (const message of batch.messages)
        console.log('RECEIVED!', message.body);
}
async queue(batch, env) {
    for (const message of batch.messages)
        console.log('RECEIVED!', message.body);
}
Note I'm not running message.ack(). I expected that this would result in the consumer repeatedly re-receiving the same message (because I never acknowledged it). But this doesn't happen; the console message shows up only once. Am I mistaken here? Or is this just a quick of local development queue simulation? 4. Is there any ETA on queues being supported with the --remote flag? This would make life MUCH easier - right now developing with queues is really quite painful. Thank you in advance.
7 Replies
Vero
Vero•2mo ago
@Pranshu Maheshwari
Mitya
MityaOP•2mo ago
Anyone able to help with any of these questions?
Pranshu Maheshwari
Pranshu Maheshwari•2mo ago
Hey @mitya! sorry for the late reply, this slipped through. Few notes: 1. wrangler tail doesn't work locally. It's really built to watch your remote worker. You don't need to run wrangler tail for your local worker - if you're just running wrangler dev you'll see the logs for your local worker written to your terminal
Pranshu Maheshwari
Pranshu Maheshwari•2mo ago
How does one configure the batch size/frequency of a queue when working locally, since the queue is automatically-created by Wrangler? That is, you don't run the create command when working locally, nor do you bind the queue explicitly to your config TOML/JSON.
Hmm you do need to bind your queue explicitly in your worker's wrangler.toml file. That's where you can define the batch settings. See here in the docs: https://developers.cloudflare.com/queues/get-started/#connect-the-consumer-worker-to-your-queue
Cloudflare Docs
Get started · Cloudflare Queues
Cloudflare Queues is a flexible messaging queue that allows you to queue messages for asynchronous processing. By following this guide, you will create your first queue, a Worker to publish messages to that queue, and a consumer Worker to consume messages from that queue.
Pranshu Maheshwari
Pranshu Maheshwari•2mo ago
Note I'm not running message.ack(). I expected that this would result in the consumer repeatedly re-receiving the same message (because I never acknowledged it). But this doesn't happen; the console message shows up only once. Am I mistaken here? Or is this just a quick of local development queue simulation?
You don't have to explicitly acknowledge messages when you're using a Worker to consume messages. If your worker returns successfully (ie: doesn't throw an unhandled exception), the messages will be acknowledged
Pranshu Maheshwari
Pranshu Maheshwari•2mo ago
Is there any ETA on queues being supported with the --remote flag? This would make life MUCH easier - right now developing with queues is really quite painful.
I hear you - it's definitely hard. We don't have an ETA right now, but we're working on it. What else has been difficult for you? If you're up to share feedback live over a call, here's a link to my calendar. Happy to help out live too with any other questions that you have: https://calendar.app.google/QAaCyRy843yDM2gH8
Appointments
Mitya
MityaOP•2mo ago
Hi @Pranshu Maheshwari - many thanks for your reply and apologies for me late one (been on leave.) You're right about needing to bind local queues in the TOML/JSON - not sure what I was thinking there. Interesting also about not needing to acknowledge queue messages consumed by a Worker. Is this documented? This is the first I've heard of that. As for feedback, sure, more than happy to have a chat. I'll book something in.

Did you find this page helpful?