Always On Azure Functions

I have a question/issue with the Always On functionality of Azure Functions. The documentation for Always On states the following:

> Indicates that your web app needs to be loaded at all times. By default, web apps are unloaded after they have been idle. It is recommended that you enable this option when you have continuous WebJobs running on the web app.

The way that is written, and the way that Always On has been described, it sounds like the Azure Function (web app) should always be loaded and ready to go; however, in practice I've noticed the following behavior that makes me feel something isn't right with how Always On is implemented:

1. When I deploy an update to an Azure Function, that update is not deployed and made ready until I invoke it once. If I'm using Always On, I feel I should rightly expect that any update will be loaded and ready to go immediately after it is deployed, so that the responsiveness of Azure Functions remains optimal. It's so bad that I've considered writing my own logic to invoke an endpoint after I update just so that the package is truly deployed and made ready, but that isn't work I should have to do myself with Azure Functions that are using an App Service Plan that supports Always On. This, in my mind, is a design issue with Azure Functions that should be corrected.

1. If my Azure Function endpoints are not busy for a period of time (not sure how long, but I've noticed this after they are idle for a bit), and then I invoke one of the Azure Functions, it takes longer than it does when it is "hot". Yet this Azure Function package is supposed to be Always On, which means it should always be "hot", should it not? The current behavior makes me feel like the package still enters a cold state from time to time and has to be warmed back up again, which again is contradictory to how Always On is supposed to function.

Am I missing something? Or is Always On not truly functioning like Always On should?