Functions Azure Blob trigger fails if I do not open the function application

Question

I have an Azure Functions function to trigger a blob trigger (so when blob is added to the container, it should fire). The function does not start until I open the function application in the portal. then he will pick up any added drops and process them as usual. Why do I need to open the function application on the portal so that my workplaces are worked? It is almost the same as a function app goes into sleep mode and then wakes up when I view it. How can I prevent this?

here is my cron

{ "bindings": [ { "name": "myBlob", "type": "blobTrigger", "direction": "in", "path": "automated-sql-export", "connection": "Conn" } ], "disabled": false } 

Answer 1

When the function application is launched, the host takes care of automatically receiving / polling new events in all of our various types of triggers (queues, event hubs, drops, etc.). However, some differences arise based on the level at which you work.

In our dynamic SKU s, we have a service external to the functional application, which is responsible for monitoring work and ensures that the Function application will work when it should be. When there is no work to do (for example, no queue messages, new drops, etc.), the Function application goes into sleep mode. Responsibility for external service is responsible for waking up when work begins.

I am our Classic SKU s (Basic / Standard), this external monitor is missing from the image. The Function application must run in Always On mode to save it. This parameter should be automatically set to "On." For you, when you create the Function app in the classic level.

Given all this background, if you work in Dynamic SKU, things should "just work." If this is not the case, please report the error here . If you are working in a classic SKU, make sure that you have Always On enabled. This is a common problem that people face.