ServiceBus trigger session issues causing active message count to spike. Trigger falls behind for ~ 1.5 hour about azure-sdk-for-net HOT 3 OPEN

Thank you for your feedback. Tagging and routing to the team member best able to assist.

from azure-sdk-for-net.

Hi @iamsamcoder. Thank you for reaching out and we regret that you're experiencing difficulties. In the majority of scenarios, a Function instance stalling is related to the Azure Functions infrastructure rather than associated with the trigger. Generally speaking, your best path forward for would be to open an Azure support request as that will allow you to engage the Azure Functions team who will have access to the platform logs and diagnostics for the period of time that you experienced the behavior.

That said, we would be happy to take a look at client logs from the trigger and offer thoughts, if you'd like. Because the trigger is a client-side construct, all of its logs are emitted in the scope of your application and would require that you had been collecting them during the time you experienced the behavior. For most applications, this flows into Applicaiton Insights using the default configuration. If you have these available and you'd like us to analyze, please share a 10-minute slice of client logs around the time the behavior was observed.

from azure-sdk-for-net.

Hi @iamsamcoder. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

from azure-sdk-for-net.