Should Azure Session Failure prevent reconnections for up to 5 minutes

Hi,

Genuine question and I personally think it's a bug so raising for a discussion point.

I'm using DAPR inside Container apps in azure.

Using a topic and session setup.

Looking at this code for the service bus subscription, it seems to block for 5 minutes max interval that prevents connections at that time.

In reality, when i have an Idle queue inside service bus e.g there's no sessions currently available.
When I do get that a message it can take up to 5 minutes to process it. Which is then a big lag for actual application level processing.

Can someone confirm if I'm reading this right and whether that's the intended behaviour? It seems odd to me.

https://github.com/dapr/components-contrib/blob/c23900d2760de2061143587c16c5e30ab3f092cf/common/component/azure/servicebus/subscription.go#L137

Read common/component/azure/servicebus/subscription.go around line 137, focusing on how session failures affect reconnection timing. Reproduce or trace the idle-queue case described in the issue and determine whether the five-minute delay is intended; done means the behavior is confirmed and any needed change is covered by the relevant component behavior or tests.

Written by the indexing model from the issue text.