hey guys, I'm using cf queue, but I'm
hey guys, I'm using cf queue, but I'm experiencing some delay to delivery the message, after publishing the message in the queue, the worker starts to process it after +30s. Do you have any idea about it?
15 Replies
I'm running a cf worker that is used as an API and also worker processing messages from this queue.
Everything is running in the JS environment and the framework used is the HonoJS.
What is your consumer configuration? Can you share the config here as-is?
e.g. did you configure a batch timeout of 30s?
I didn't found this batch timeout config @elithrar
@Pranshu Maheshwari the queue id = 6fcbbbd468a5459e81a29a8bb56bb577 and account id = 9161f3bf7875fc457efb6c4fc392e289
anyone could help me?
Hey! just checked, could you confirm for me if you're still sending data to this queue? I see only a small amount of activity here, from yesterday and a small amount of activity a month ago, ~and everything looks normal from our side in the logs / metrics~ (Edit: it does actually look like it's taking 30s for messages to get picked up)
Could you share your consumer worker code with me, along with the wrangler.toml you're using for your consumer? feel free to dm me if you'd prefer
I'm sending in your DM
I’m experiencing a similar issue - queue consumer seems to get stuck and waits for cpu timeout before moving to the next message. I’ve experienced it on three queues consumers, but I was able to roll back one to a version from a week ago and I’m not experiencing the issue there. Haven’t changed my wrangler.toml, batch config, or core of my queue handler in that time. Did either of you find a solution here? @0xthierry @Pranshu Maheshwari
Could you share a few things with me:
- queue ID & account ID
- your consumer code
feel free to DM me if you'd prefer
waiting for cpu timeouts is most likely a different issue than the one from the top of this thread
Sent you a DM! Thanks in advance for any help
Hi @Pranshu Maheshwari , I'm also having the similar issue (Stuck in the queue; producing message works, but consuming doesn't). I can provide information via DM, so could you check it for me just this once, too?
yes please 🙂
Update for anyone else experiencing this: current conclusion (from Pranshu) is that this appears to be a bug on cloudflare's end, some people have reported disconnecting/reconnecting the consumer works, for me the disconnect/reconnect results in the first message going through followed by the same 30s delay for the second message (no change in behavior, I think the 30s delay relates to the consumer finishing/releasing the message incorrectly but can't verify). I also tried making a new queue and connecting my producer/consumer to that queue, no change. Tried deploying my consumer code using older versions of wrangler (from before I was experiencing the issue), no change. The only thing that's worked for me is rolling back my consumer code to a deployment before I experienced the issue (first deployment of live with bug 8/12, previous [no bug] deployment was 8/5). Not sure why this works for me (can't find a way to see what cloudflare is using as the deployed consumer code vs the current deployment's code), but it does.
Tried deploying my consumer code using older versions of wrangler (from before I was experiencing the issue), no changeWrangler is just a client, so it won't change anything. The client code it bundles isn't the issue here.
for folks on this thread: we've identified the issue causing 30s delays in @luiseok's account. we're rolling out a fix this week. still working on the issues for other accounts!