Azure Function with correct StorageConnectionString works locally, fails in production

1
votes

I have an Visual Studio 2019 developed azure function (v3) that is deployed via devops pipeline when the webapp is deployed. It looks like this:

    [FunctionName("GetUserCoordinatesFunction")]
    public async Task Run([QueueTrigger("getusercoordinatesquery", Connection = "AzureWebJobsStorage")] GetUserCoordinatesQuery request, ILogger log)
    {

This function works perfectly locally. If I emulate storage, it works... if I replace my storage string with my production storage connection string, it still works.

enter image description here

In other words, my app writes messages to the storage without any issue.

I've double checked, triple checked, quadruple checked my AzureWebJobsStorage string in Azure Function Configuration... everything is correct!

In production only, my function "GetUserCoordinatesFunction" does not detect messages in queue. Why? Please and thanks.

I tried this, but I'm on v3 and that didn't fix it Azure function implemented locally won't work in the cloud

1
c#azure.net-coreazure-functions
Could you please share the function.json of your function on portal ? - Hury Shen
@HuryShen do you mean the host.json? - CSharpMinor
No, I mean this file on azure portal. - Hury Shen
Have you successfully deployed it now ? Have you solved the problem ? - Hury Shen
I'm still not sure what the issue with my deploy pipeline. I'm investigating that now. But after I published the function directly from VS it did show up in my functions list. ...unfortunately there is some other unrelated code that needs to be refactored before the function works as intended, but I would mark this specific post as solved for me. Yes you may post an answer for this - CSharpMinor

1 Answers

1
votes

Summarize the comments above. According to the screenshot you provided, it seems the deployment didn't success. Just deploy the function from VS to azure again.