Azure Service Bus Explorer returning error when peeking messages

Mariana 31

When using the Azure Service Bus Explorer to peek messages either in queue or deadletter, an error appears with the following message:
Failed to peek messages - TypeError: Cannot read properties of undefined (reading 'omitted-message-body-size')

User's image

Messages were added to the queue via REST API (PHP). When a message is added through the Explorer, it can be peeked successfully. Can you please suggest an alternative to peek messages?

Hugo Giordano 5 Reputation points

2023-07-03T15:58:46.79+00:00

Same to me
Andre Pedroso 5 Reputation points

2023-07-03T16:26:35.9033333+00:00

I have the same issue.
Brad Lumb 0 Reputation points

2023-07-03T22:41:08.6933333+00:00

Also have the same issue. Thought it may have been a software issue on our side until I've seen these messages who's timing align exactly with when we started seeing this error too.
Andre Pedroso 5 Reputation points

2023-07-04T09:11:23.2566667+00:00

Hello! It seems to be working fine now. I no longer get the client-side error. Cheers
Hugo Giordano 5 Reputation points

2023-07-04T14:32:42.0533333+00:00

It still doesn't work for me. So, I have 2 topics, where only one is getting this issue.
Hugo Giordano 5 Reputation points

2023-07-04T14:54:00.0866667+00:00

It was an cache issue; after signed out and clearing my cache, it started to work properly.
MayankBargali-MSFT 70,796 Reputation points

2023-07-06T09:26:15.4833333+00:00

@Mariana Apology for the inconvenience due to this issue. Can you please confirm if you are still facing the issue?
Mariana 31 Reputation points

2023-07-06T11:27:08.9833333+00:00

@MayankBargali-MSFT it seems to be fine at the same that that Andre mentioned it was working.
MayankBargali-MSFT 70,796 Reputation points

2023-07-11T04:54:13.88+00:00

@Mariana Thanks for the confirmation.

1 answer

MayankBargali-MSFT 70,796 Reputation points

2023-07-11T04:57:10.7466667+00:00

In case someone observe the same behavior. Please try to clear the browser history, try different browser/network to confirm if you still observe the similar behavior. In case if someone still observe the same issue then please collect the portal F12 traces from browser and session ID (ctrl + alt + d) along with the timeframe after reproducing the issue and share those details to assist you further.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure Service Bus Explorer returning error when peeking messages

1 answer

Your answer