Azure Function app stops processing Storage Queue for > 10 hours. (Premium Elastic)

#### Investigative information

Please provide the following:

- Timestamp: Last invocation before pause, 2023-11-28T17:21:20.6908991Z. Next invocation after pause, 2023-11-29T07:07:10.7668843Z

- Function App version: Python v2.0 Azure Function
- Function App name: thumbnailgenerator-app-westeurope-prod
- Function name(s) (as appropriate): thumbnailgenerator
- Invocation ID: Last invocation before pause, e02d25fe-3c28-4daf-9557-850774a5ecb3. Next invocation after pause, e02d25fe-3c28-4daf-9557-850774a5ecb3
- Region: West Europe

#### Expected behavior

The Azure Function is invoked when a message is added to the Azure Storage Queue that the function is bound to.

#### Actual behavior

The Azure Function stops being invoked for messages for ~10 hours for no observable reason. New messages are added to the queue in between the two invocations given above, but the messages remain unprocessed on the queue.

#### Known workarounds

None other stop using Azure Functions for this functionality.

#### Related information

Python 3.7
v2.0 model
Azure Storage Queue binding

The Azure Function is auto scaled down around the same time as the last invocation before the pause from 2 instances to 1. The Az function remains at 1 instance for the time period when it should be processing messages, before spiking up to 3 instances when it starts processing the backlog of messages.

No source files, tests, or entry points are named. Start by reviewing the Azure Storage Queue binding and the reported invocation and scaling timestamps, then trace how queue polling behaves during the single-instance period. Done means identifying the cause of the processing gap and documenting or validating a reproducible fix.

Written by the indexing model from the issue text.