Azure Question posted in
The official documentation to get you started can be found here.

Service Bus trigger not working in Azure portal but works locally with Node.js v4 Azure Functions

I’m using the Node.js v4 programming model for Azure Functions, and I have a Service Bus-triggered function with the following setup:

app.serviceBusQueue('MyFunctionName', {
  queueName: 'myQueueName',
  connection: 'ServiceBusConnectionString',
  handler: azureFunction,
  isSessionsEnabled: true,
});

Host.json:

{
  "version": "2.0",
  "extensionBundle": {
    "id": "Microsoft.Azure.Functions.ExtensionBundle",
    "version": "[4.0.0, 5.0.0)"
  },
  "functionTimeout": "00:04:00",
  "extensions": {
    "serviceBus": {
      "prefetchCount": 10,
      "messageHandlerOptions": {
        "maxConcurrentCalls": 16,
        "autoComplete": true,
        "maxAutoRenewDuration": "00:05:00"
      }
    }
  }
}

Node.js runtime version: 18

Works locally with func start, but messages aren’t processed when deployed to Azure portal.

I’ve verified that:

  • The connection string is correctly set in Azure’s Application
    Settings (without EntityPath).
  • The runtime version in both local and Azure portal is v4.
  • The Function App is running and not in a stopped state.
  • The queue name and connection match the function definition.

UPDATE:
checking insights I could see the error

The 'MyFunctionName' function is in error: The binding type(s) 'serviceBusTrigger' are not registered. Please ensure the type is correct and the binding extension is installed.
Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    So, after a few hours, I finally discovered what the problem was:

    I have a monorepo from which I deploy different function apps. The issue was that the host.json file were not located in the root directory of the function app after deployment.

    To check this I went to:

    https://<functionAppName>.scm.azurewebsites.net/DebugConsole

    Then into site and then wwwroot folder.

    Ensure that host.json is there and it is well configured. If it is missing or incorrectly configured, the Azure Functions runtime may not recognize extensions.


  2. 0

    I have used the given code and have followed below steps to achieve it.

    import { app, InvocationContext } from "@azure/functions";

export async function serviceBusQueueTrigger1(message: unknown, context: InvocationContext): Promise<void> {
    context.log('Service bus queue function processed message:', message);
}

app.serviceBusQueue('serviceBusQueueTrigger1', {
    connection: 'ServiceBusConnectionString',
    queueName: 'myqueue',
    handler: serviceBusQueueTrigger1,
    isSessionsEnabled: true
});

    Post deployment, I fetched connection string and added in Environment variable as shown below.

    enter image description here

    enter image description here

    Function got triggered upon sending a message in service bus queue.

    enter image description here

    If it still doesn’t fires then check the associated application insight in case of any errors.

    enter image description here

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search