Hello, is there an issue with queues at
Hello, is there an issue with queues at the moment? I've got messages being reported as being in my deadletter, however I can't see them when listing messages and nothing else is reading from the queue 🤔
23 Replies
no general issues right now, but there might be a bug here! how are you seeing messages as reported in your DLQ? are you looking at the dashboard?
you might know this already but just in case, the dashboard shows the average backlog over the specified time period, not the current live backlog
Looking at the metrics from the queue which is showing messages should be in the deadletter
But then listing on the deadletter they do not show
I thought maybe it was some internal delay but it's been overnight and still nothing has appeared
@Pranshu Maheshwari I've checked again to see if there was any further delay and nothing has appeared so looks like messages haven't been delivered, is there anything you could check on your side please 🙏
@Pranshu Maheshwari this is definitely an issue across multiple of my queues. Please would you be able to help me with this as its impacting my business
100 have been reported as deadlettered here but I can't see those in my DLQ
Also I've got 2 messages in the DLQ that I can't acknowledge. Really not sure what's going on
Also raised this case 01257963 as its really impacting my business/service to my customers 😢
Hey @jordanfinners, could you send me over your account ID & queue IDs?
both for your primary queue and your DLQ
Yeah it's affected multiple queues but I'll send the most pressing one 😊
Queue ID b1368eea661b4d74bc8894e5dab8934b
DLQ a12fb186ec914f899d64e7044a284780
Account ID 3bfe7ad335003f84c4a9959ad57216de
Thank you! Sorry for chasing so much but had to manually recreate over 400 messages over the weekend while my customer was on a short timeline
Ofc! just to confirm, have I understood this right?
- You're sending messages to your primary queue, b1368eea661b4d74bc8894e5dab8934b
- There are 100 messages that were reported as delivered to your DLQ a12fb186ec914f899d64e7044a284780
- But a12fb186ec914f899d64e7044a284780 doesn't have those messages when you list them in the dashboard, and you're not able to acknowledge a couple of the messages that are listed there
By the way, as far as I can tell, a12fb186ec914f899d64e7044a284780 has several messages in the backlog. Several messages were written to that Queue on Nov 3 in particular.
But: it's possible there's a frontend bug on your account. We saw a few failed requests for the endpoints that our dashboard uses to preview & acknowledge messages in your acct
We found the bug: we're working on a fix! the bug is causing your dashboard view for Queue a12fb186ec914f899d64e7044a284780 to be "stuck" on two messages.
the rest of the messages are still in the DLQ, they're just not appearing on the dashboard. should be resolved once we have our fix deployed!
@jordanfinners
Yeah that's correct
It's happened in my reports queue as well
I assume this bug will fix it in all of them?
Also please could I ask for a send batch or deadletter redrive button in the UI as a future feature it would be a life saver 😅 please 🙏
Thank you so much for investigating this for me! I'm glad I wasn't going mad 😂
redriving messages is on the roadmap! it's planned for this quarter, although realistically it might get shipped early Q1 2025
yes, but just in case, could you send me the Queue IDs for the affected queues?
Queue ID 4965d3ae9ace413096703251979f14a5
DLQ 5c71988d2c8942c0b7eeccb143e0c696
Hey @jordanfinners, we pushed out a fix for this a few days ago! Could you let me know if it's working as expected now?
Hey, I can still only view the 2 failed items in the queue stuck on 2 messages 🙈
argh - let me track this down. sorry about this, must be very frustrating for you!
@jordanfinners it looks like these are messages that were in a v1 queue and are stuck there after we migrated to v2 of queues (the current version). Have you connected a consumer to drain messages from the queue?
I haven't, I'll delete those 2 messages as I don't need them now. Then should that resolve it? 🤔
It should, yeah, as messages should now be sent to your v2 queues. But if you still see an issue, please let us know. 🙂
Hey, I've deleted those messages now, but I can't see the new deadletter messages, will they take some time to come through?
Also not sure if its related but each time I try and view my queues I get this error
Looking through the console, its because service name is ""
I think we have a dashboard bug here - we'll sort this out. thank you!