Occasionally Function App Time Trigger type doesn't get executed at a scheduled time due to Instance Node change.
My Function is set to execute every 20 seconds and occasionally it experiences few seconds delays or doesn't start at all.
Azure Support has done backend log checks and attributed this behavior to Instance Node change.
This affects both classic and durable functions.
Can you please improve this behavior so this problem doesn't occur.
Our function is too light for even the most basic dedicated service app plan. We want to keep this function costs down and hence would like to continue using the Consumption plan.