Service bus topic trigger doesn't trigger on portal?

Bhavana yalamanchili 1

I have created an service bus topic trigger in vs 2019. The function version is V3. The service bus topic triggers fine in local but when deployed to portal it doesn’t trigger. Looked for different solutions and options and found that in function.json the direction attribute “in” was missing in the binding. The service bus topic trigger works fine if it’s created in portal but the issue comes when the function is deployed to portal since it’s not generating proper function.json file. Can you please help us out how to fix the issue with function.json file?

Pramod Valavala 20,656 Reputation points Microsoft Employee

2020-07-10T09:44:07.273+00:00

Could you share how you are deploying your function app? Also, do mean the manual trigger from the portal itself, or does the function not trigger even for a service bus message?
Bhavana yalamanchili 1 Reputation point

2020-07-10T12:14:21.77+00:00

The code is deployed through CI/CD pipeline.

When the service bus topic trigger function is created directly in Azure portal, the function triggers and it picks up the message from the topic provided. The same function when deployed either from vs code or through CI/CD pipeline doesn’t trigger at all.
Pramod Valavala 20,656 Reputation points Microsoft Employee

2020-07-10T12:33:43.513+00:00

Could you confirm if the required App Settings are present? By default, when deploying from VS Code, the local settings are not pushed.

Based on this comment, the direction property is not present by design and should not causes issues for the running of the function, just the portal UX.
Bhavana yalamanchili 1 Reputation point

2020-07-10T12:57:41.553+00:00

All the properties in the app settings file are configured under Configurations in Azure portal. The only difference i see in the direction attribute in bindings which is missing in function.json file when deployed through vs code or CI/CD pipeline. When triggered manually in portal under code+test also work fine, the issue is the service bus topic trigger should trigger itself when there messages in the specified topic.
Bhavana yalamanchili 1 Reputation point

2020-07-10T13:01:00.863+00:00

function.json when deployed through CI/CD pipeline

{
"generatedBy": "Microsoft.NET.Sdk.Functions-3.0.2",
"configurationSource": "attributes",
"bindings": [
{
"type": "serviceBusTrigger",
"connection": "ServiceBusConnectionString",
"topicName": "equiplistposted",
"subscriptionName": "ghostequiplist",
"name": "serviceBusMsg"
}
],
"disabled": false,

}

Function.json when created the function on portal

{
"bindings": [
{
"name": "mySbMsg",
"connection": "ServiceBusConnectionString",
"topicName": "equiplistposted1",
"subscriptionName": "ghostequiplist1",
"direction": "in",
"type": "serviceBusTrigger"
}
Pramod Valavala 20,656 Reputation points Microsoft Employee

2020-07-10T14:33:18.037+00:00

Based on this comment, the direction property is not present by design and should not causes issues for the running of the function, just the portal UX.

As mentioned above, the property should not affect the function runtime.

Could you confirm if no other function (the one locally) is not running when the function is deployed? If so, it is possible the local function is handling the message before the one deployed in Azure.
Bhavana yalamanchili 1 Reputation point

2020-07-10T15:41:58.097+00:00

The local function is not running after deployed to Azure portal and is not picking that messages. When i manually edit the function.json in Azure portal it works fine but every time new deployment is done function.json file is generated again and it causes issues in PROD.
Pramod Valavala 20,656 Reputation points Microsoft Employee

2020-07-15T11:52:27.473+00:00

While usually not required for most deployment options, could you check to see if syncing triggers post deployment helps?
Pramod Valavala 20,656 Reputation points Microsoft Employee

2020-07-21T10:38:05.33+00:00

@Bhavanayalamanchili-5537 Just following up here to see if syncing triggers helps.

Share via

Service bus topic trigger doesn't trigger on portal?

Your answer