Function App trigger stops listening to messages from Service Bus Queue

Anuja Mittal (Admin) 0 Reputation points
2023-08-17T11:50:28.42+00:00

We have a service bus with some queues set up in it and a function app trigger which processes the messages sent by service bus. Our service bus will receive message from a third party system and the message will be processed by the function app trigger.

ISSUE:

Function app trigger stops consuming/processing the messages, if there are no messages received by the service bus for some time then function app stops. If then next batch of messages come, they will queued in the service bus and will be processed only when we restart the function App.

Azure Service Bus
Azure Service Bus
An Azure service that provides cloud messaging as a service and hybrid integration.
548 questions
Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,293 questions
Azure
Azure
A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.
943 questions
{count} votes

1 answer

Sort by: Most helpful
  1. JananiRamesh-MSFT 21,321 Reputation points
    2023-08-18T17:15:07.6766667+00:00

    Hi Anuja Mittal (Admin) Thanks for reaching out. could you please confirm if your Function app is on dedicated plan? This can happen if the function app is on dedicated plan and always on is not enabled.

    Reference: https://learn.microsoft.com/en-us/azure/app-service/configure-common?tabs=portal#configure-general-settings

    For other plans, if this is happening, we might have to investigate.

    Please share the below details over an email at AzCommunity@microsoft.com ( with subject "Attn: Janani") and include the below details:

    • Your Azure Function Name
    • You Azure Function App resource URI in below format: /subscriptions/XXXXXXXXXX/resourceGroups/XXXXXX/providers/Microsoft.Web/sites/XXXXXX
    • Most recent UTC time of the actual issue.

    I will look at the backend logs to identify the root cause.