Unclear exception from broker

[SeanFeldman]

When setting up a forwarding queue using the following code

var connectionString = Environment.GetEnvironmentVariable("AzureServiceBus_ConnectionString");
var client = new ManagementClient(connectionString);

var queueDescription = new QueueDescription("MainQ")
{
    RequiresSession = true  
};
var forwardingQueueDescription = new QueueDescription("TempQ")
{   
    RequiresSession = true, // disabling Session will allow the broker to pump the messages and forward to the destination
    ForwardTo = queueDescription.Path
};

await client.CreateQueueAsync(queueDescription);
await client.CreateQueueAsync(forwardingQueueDescription); // exception is thrown

an exception is thrown

SubCode=40000. Bad Request. TrackingId:ec9a3f45-7315-4974-9c4d-3cb374a48720_G19, 
SystemTracker:seanfeldman-test.servicebus.windows.net:TempQ, Timestamp:2019-10-11T17:12:38

The information provided in the exception does not elaborate on the reason the forwarding queue creation is failing. I suspect that's because of the sessions being enabled on the forwarding queue and the hidden behind the broker message pump that receives and forwards to the destination queue (MainQ) is by default set up as a receiver w/o sessions enable?

Actual Behavior

Unclear exception

Expected Behavior

Clear exception message or work as expected, similar to how entities w/o sessions enabled work when forwarding is set up.

[SeanFeldman]

Fixing the exception message would be the best as the broker works as designed. Saying that it still feels like the broker internals bleeding out.

[EldertGrootenboer]

We have added a backlog item to update the exception message.

[EldertGrootenboer]

Thank you for your feedback. We have brought this item in our current semester, and should be able to provide an update in the coming months.

[EldertGrootenboer]

We have brought this item in our current planning. We don't have a specific date when development will start for this, once we have more information around this, we will update this thread.