Azure Function Service Bus trigger goes idle when no messages are present in the Topic (Consumption Plan)
- Dominant language
- PowerShell
- Stars
- 1.1k
- Forks
- 215
- Avg merge
- 4h 2m
- Merged PRs (30d)
- 1
Description
Hi,
We are encountering a strange issue / strange behaviour in our Azure Service Bus Trigger.
The purpose we are trying to fullfill:
- Everytime a message is sent to the Service Bus Topic, we would expect that (even after a short delay ..) the trigger picks up the message and the function processes this.
The error / issue that we encounter:
- It looks like, after the function initially processed all the messages in the Topic, the function goes idle and it doesn't automatically wakes up when new messages are present on the Service Bus Topic.
We checked a lot of possible scenarios & analyzed the behaviour:
- Going to the UI of the function or the parameters in the portal wakes the function up
- Scrolling through the appsettings in the portal wakes the function up
- Redeploying through CI/CD also wakes the function up
Then, after the function processed all the messages in the topic, it goes idle again and it doesn't wake up automatically.
I've already read a lot of issues on this but those trace back to 2017-2018 and all the issues were related to the connectionstring not having 'Manage' access so the scale controller could not fire. We use a connectionstring and the connectionstring has manage rights so this issue should in our case not be present.
Time Range (UTC +2):

Function Log:
2023-05-31 09:24:50.918
Executed 'LoggingOrchestrator_EventTrigger' (Succeeded, Id=c2ddddbd-51eb-4387-a550-7d4113f881ed, Duration=194ms)
Host.json


_Kindly let me know if you require more information or logs on this issue and i'll gladly provide those._
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.