Peeking ServiceBus messages does not contain any information about if it's deferred or not

• Package Name: azure-servicebus
• Package Version: 7.0.1
• Operating System: Linux RHEL 8
• Python Version: 3.9

Describe the bug Peeking messages does not contain information whether it’s deferred or not.

To Reproduce Steps to reproduce the behavior:

1. Defer a message
2. Peek messages:

>>> metro_client = ServiceBusClient.from_connection_string(conn_str="my_conn_str'', transport_type=TransportType.AmqpOverWebsocket)
>>> receiver = metro_client.get_subscription_receiver(topic_name='my-sub', subscription_name='sub-my-sub-example')
>>> messages = asyncio.run(receiver.peek_messages(5, sequence_number=5))  # Get the message you want
>>> message = message[0]
>>> message._is_deferred_message
False

Expected behavior I expect the message to be marked as a deferred message, or have any indication that it is such.

What I want to achieve There might be a better way of doing this (e.g. with dead letters?), so I’ll explain the use case, in case there’s a better solution:

• Have a container receive messages
• Mark the message as something, so that I can pick it up later
• Start a background task (through Celery) based on the subject of the message
• The background task will then fetch the message and mark it as completed when the task is completed

Now, if the background task for some reason would fail, I need to be able to fetch all the messages that never was completed (in my current case deferred), I can decide how to act on them. I wanted to do this:

• Fetch all deferred messages and show them to the user (GET API using peek)
• A user can select messages and retry them through sending a POST request to our API with the sequence number of that task. Our backend would then fetch that message and execute the task. When the task is completed, the message would be marked as such.

[ramya-rao-a]

The GitHub repo for feature requests for the service is https://github.com/Azure/azure-service-bus

Related issues to the one being discussed are https://github.com/Azure/azure-service-bus/issues/442 and https://github.com/Azure/azure-service-bus/issues/95. Please participate in these issues to get input from the service team.

Closing this issue as there are no planned next steps from the SDK perspective.

As and when the service implements this feature, we will incorporate it in the SDK

[msftbot[bot]]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jfggdl, @axisc.

Issue Details

---

• Package Name: azure-servicebus
• Package Version: 7.0.1
• Operating System: Linux RHEL 8
• Python Version: 3.9

Describe the bug Peeking messages does not contain information whether it’s deferred or not.

To Reproduce Steps to reproduce the behavior:

1. Defer a message
2. Peek messages:

>>> metro_client = ServiceBusClient.from_connection_string(conn_str="my_conn_str'', transport_type=TransportType.AmqpOverWebsocket)
>>> receiver = metro_client.get_subscription_receiver(topic_name='my-sub', subscription_name='sub-my-sub-example')
>>> messages = asyncio.run(receiver.peek_messages(5, sequence_number=5))  # Get the message you want
>>> message = message[0]
>>> message._is_deferred_message
False

Expected behavior I expect the message to be marked as a deferred message, or have any indication that it is such.

What I want to achieve There might be a better way of doing this (e.g. with dead letters?), so I’ll explain the use case, in case there’s a better solution:

• Have a container receive messages
• Mark the message as something, so that I can pick it up later
• Start a background task (through Celery) based on the subject of the message
• The background task will then fetch the message and mark it as completed when the task is completed

Now, if the background task for some reason would fail, I need to be able to fetch all the messages that never was completed (in my current case deferred), I can decide how to act on them. I wanted to do this:

• Fetch all deferred messages and show them to the user (GET API using peek)
• A user can select messages and retry them through sending a POST request to our API with the sequence number of that task. Our backend would then fetch that message and execute the task. When the task is completed, the message would be marked as such.

Author:	JonasKs
Assignees:	yunhaoling
Labels:	Client, Service Attention, Service Bus, customer-reported, feature-request
Milestone:	Backlog