Azure Queue Trigger Function not firing

Question

I have designed a Azure Queue Trigger function in Python with the following functionalities.

When a message is added to Queue named Input , the function fires
It processes the message added to the Input Queue and stores the result in Output Queue

Now my problem is this is working fine when I run locally . But after deploying the function app and then if I add a message to the Input Queue , the function is not firing .

Checked everything . Here is my function.json for reference .

I havent been able to locate anything relevant to this in documentation and not sure what I'm missing .

{
  "scriptFile": "__init__.py",
  "bindings": [
    {
      "name": "msg",
      "type": "queueTrigger",
      "direction": "in",
      "queueName": "input-messages-queue",
      "connection": "AzureWebJobsStorage"
    },
    {
      "type": "queue",
      "direction": "out",
      "name": "outputmessage",
      "queueName": "output-responses-queue",
      "connection": "AzureWebJobsStorage"
    }
  ]
}

Is the setting AzureWebJobsStorage available in your Function App configuration? Are the queues available in the storage account it points to? — rickvdbosch
– rickvdbosch, Commented Jun 5, 2020 at 14:40
Hi thanks for the quick reply . I checked the Application Settings of my Function app and could see an entry called AzureWebJobsStorage and the queues in question are present inside a single storage account . — Rajesh Rajamani
– Rajesh Rajamani, Commented Jun 5, 2020 at 14:50
Hi , figured out my mistake . I created the queues in a different storage-account . But the function was pointing out to the storage-account where it was created within a different resource group. I created those queues in the same storage-account and voila it worked . Thanks for the guidance .. — Rajesh Rajamani
– Rajesh Rajamani, Commented Jun 5, 2020 at 15:07

Nishat Sayyed · Accepted Answer · 2021-03-02 13:10:37Z

9

In my case I forgot to add the settings from my "local.settings.json" file in "Configuration" of the Azure Function App in the portal. Not doing this will not add the connection string for the queue and your function will never be triggered.

answered Mar 2, 2021 at 13:10

Nishat Sayyed

1512 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Lucas Over a year ago

Same problem here, your answer solved it. There should be some sort of warning for that from Azure.

Huy Truong Over a year ago

I got the same problem that missed connection string value from local.settings.json file & fixed. Thanks

Rajesh Rajamani · Accepted Answer · 2020-06-07 07:04:19Z

2

figured out my mistake . I created the queues in a different storage-account . But the function was pointing out to the storage-account where it was created within a different resource group. I created those queues in the same storage-account and voila it worked

answered Jun 7, 2020 at 7:04

Rajesh Rajamani

5811 gold badge6 silver badges18 bronze badges

1 Comment

NOP-MOV Over a year ago

having the same issue, nothing happens, no logs, no errors. But my mine are in the same storage account.

Daniel D · Accepted Answer · 2022-05-06 01:12:08Z

In Visual Studio 2022, bindings to Azure Queue are stored in local.settings.json config files for local execution, for example:

{
  "IsEncrypted": false,
  "Values": {
    "AzureWebJobsStorage": <Azure Storage Key 1 - taken from Azure Portal>,
    "FUNCTIONS_WORKER_RUNTIME": "dotnet",
    "azurestoragetest": <Azure Storage Key 1 - taken from Azure Portal>  }
}

<Azure Storage Key 1> is Access Key for Azure Storage stored in Azure Portal.

However, when Azure Function is Published to Azure, the values for the bindings are not published (deployed) until set specifically in dependencies.

In VS select project, right click and choose Publish. On Publish page go to Service Dependencies, locate Azure Storage, click "..." to open Edit dependencies menu. From there on 2nd page there is option "Save connection string value in" - set it to Azure App Settings. By default, this setting is set to "None" - meaning Publish will not store bindings values in Azure.

The json config file in Azure for Azure Function stores only bindings, but not values of these bindings (for security reasons), so it doesn't tell us whether bindings are assigned any values or not.

klenium · Accepted Answer · 2020-11-10 11:36:33Z

0

Make sure the configuration entity is set up in the portal. I was using a custom config key for the connection name, but did not set the value for it, only locally, so the queue did not trigger the function running in the cloud.

answered Nov 10, 2020 at 11:36

klenium

2,6372 gold badges28 silver badges52 bronze badges

Comments

forero08 · Accepted Answer · 2023-10-06 19:15:29Z

0

I was in a similar situation and it turns out that the app_offline.htm file was accidentally deployed. I thought that it was only affecting the process of browsing the base URL of the function or disabling the HTTP functions, but it is actually stopping the queue triggers as well.

Check your root folder and if that file is there, you just need to remove it.

edited Oct 6, 2023 at 19:15

answered Oct 2, 2023 at 20:33

forero08

11 silver badge3 bronze badges

Collectives™ on Stack Overflow

Azure Queue Trigger Function not firing

5 Answers 5

2 Comments

1 Comment

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

2 Comments

1 Comment

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related