HttpContext.Current sometimes lost during async Entity Framework 6 query. What's the difference between the call stacks?

Question

I\'m debugging some code and noticed that occasionally, when it accesses the HttpContext.Current it is null and resorts to a fallback that was put in to handle that