Stopping / Killing Azure Functions Running Instances on Consumption Plan

Question

How do u kill azure function runnable instances (executions) on a Comsumption Plan (previously known as Dynamic Plan).

I am running the azure function on a runtime version of 1.0.

• Few (some not shown in the log in the screenshot below) were running past the FIVE MINUTES functionTimeout threshold (check the one with DOTTED status).
• There were however few instances that DID get killed AS expected when they reached the FIVE MINUTES THRESHOLD (check the one with CROSSED status)

What I tried:

• As suggested in this SO question Stop/Kill a running Azure Function I restarted the website hosting the azure function
• I even stopped / started the website just to be sure
• I killed the processes from kudu interface but the logs still keep showing there was a rouge instance.
• Process explorer showed 32 Threads but all of them were in WAITING status. Nothing was running from what I could observe.

Finally

• I deleted the website and moved over a App Service Plan based function since that seems to be the only option azure functions which need flexible timeouts.

Answer 1

This is a monitoring bug, and although it looks confusing, would have no impact on the runtime behavior.

I have opened an issue to track this here and it will be updated as we make progress.

Thank you for your patience with this and for reporting the problem!