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
@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
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 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?
Hey, I've checked my queues, as I thought I would give it a while incase of any caching etc. But I still can't see any deadletter messages or even metrics for that queue now
Would it be possible to organise a call in the new year? So we can go through/debug this together, as it might be quicker/easier than back and forth, if possible? please