Consumption Plan - Azure Function Service Bus Trigger does NOT spin up instance when new messages are received after period of inactivity

Question

I have a function app that works fine locally, and when it runs in Azure it runs without error. The problem is when no messages are added to the queue for a stretch, the Job Host shuts down (I've confirmed this in the logs) and doesn't start back up when new messages are added to the queue. Only navigating to the app in the portal causes it to finally start up.

This isn't a cold start problem, I've watched messages pile up on the queue for over an hour.

I've confirmed that my functions triggers are synced, as that seemed like it used to be the main cause of this issue.

Answer 1

Hey! Let me guess, you are using Managed Identity between Azure Function and Service bus? In this case, you have to get rid of Managed Identity and it will work.