Allow trigger prioritization
I have several functions including both http and queue triggered, as well as one timer triggered, in a single function app on a multi-instance app service. I am having problems where even though there are multiple instances, some of my functions wind up waiting until the timer triggered function (which takes a few minutes) is complete before they execute. That means that instead of taking less than a second, these functions take several seconds up to minutes, depending on when they are triggered during the timer's execution. I am probably going to move the timer triggered function to its own function app on its own, much smaller, app service plan, but thinking about this, I realized that the turn-around time on most of my functions doesn't really matter, but one of the http triggered functions is actually user-facing. That means there is literally a user sitting there waiting while this function executes, so it would be nice if we could have that function prioritized to jump the line so that it gets processed as soon as possible. Obviously, I don't want one user's request to jump in front of someone else's. So, for example, suppose I have functions A, B, and U, where U is the user-facing function. If the queue of events right now is UABA and another U comes in, it'll be stuck on the end: UABAU. What I want is for it to be inserted after the first U and before the A: UUABA.