Azure / Azure/azure-functions-host

debugging a "never finished" function

Open
#1,780 8 comments 2 reactions 0 assignees View on GitHub
needs-investigation question
Dominant language
C#
Stars
2k
Forks
482
Avg merge
2d 12h
Merged PRs (30d)
38

Description

I recently moved my webjobs + scripthost setup to an Azure Function app. This transition was fairly smooth.

Last night, I finally made the swap from my staging slot to production. Unfortunately, a number of my functions runs went into a "never finished" state with a 0ms run time. There is nothing that I can see in the logs to make any sort of diagnosis.

What typically causes a function to enter this state? How best to debug it?

Thank you!

Contributor guide

Open the contributing guide

Research direction

The report names no source files or tests; begin by examining Azure Function runs that show “never finished” with 0ms and compare staging and production logs after the slot swap. Done would be a reproducible cause and a documented debugging path.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.