azureservicebus - Azure Service Bus Queue client-side durability -

When using the brokerage message for the service bus quote, I think the cloud queue is only durable whether this client-side Affects too?

For example, when I send the message to the queue, I should handle the situation manually when either the transaction will be dismissed due to the connection throttling problem, or it will automatically be on the client Anything else remains and send back again?

There is no "automatic" caching or storing of messages service bus QueueClient Object or Library If QueueClient.Send (message) is successful without the call exception, the message is guaranteed to be durable. If an exception has been raised then this indicates failure (due to connectivity / throttling etc.). If you want to make your client flexible enough to drop the connection, you may consider sending a message like MSMQ using a local queue may fail. We have a sample that shows how to transmit messages between MSMQ and line of service bus: