Azure / Azure/Azure-Functions

Azure Function in Consumption Plan not processing from Azure Storage queue after idle period

Open
#823 5 comments 0 reactions 1 assignee Claimed by @fabiocav View on GitHub
Dominant language
PowerShell
Stars
1.1k
Forks
215
Avg merge
4h 2m
Merged PRs (30d)
1

Description

I have a few Azure Functions deployed as a .Net Standard library that went idle due to no messages being inserted into the queue for a little over a week. Despite new messages being in the queue, the function is not being run; the messages are remaining in the queue.

I've also tried redeploying the services, restarting them, and viewing them via the portal, each of which sound like they're suggested solves in other issues (#370 and #389). I hope to be pointed to documentation that helps me understand what I did wrong, or otherwise provide that information to future developers.

I have a hunch that the "central listener service" (mentioned in #370) is having issues determining the queues it should listen to, but I can't find any logs to that effect, nor am I sure how it should be set up for a storage queue rather than a service bus.

My function app can be found at "Central US, East US 2", and the last successful run was Id=92160a7f-f115-4049-a88d-1a91da8229b8 at 2018-05-18T20:39:42.816. (I pulled the information according to https://github.com/Azure/azure-functions-host/wiki/Sharing-Your-Function-App-name-privately from my application insights logs.)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.