Reputation: 11
The queue function is working fine in the developer machine. But once published to Azure, after a day or two, the function is not picking the queue message. the queue message is displayed in the Storage Account queue and not dequeued.
When we are using the Run command in monitor then it is picking the queue message and processing successfully.
For your Information: Not access issues, all application and id and secrets are correctly configured, all hosted in the same tenant, No exceptions generated.
Upvotes: 0
Views: 1383
Reputation: 1
Azure function (consumption) goes into idle or inactive state when not in use for some period so it requires to be pinged somehow. That is also known as cold start. To get rid of a cold start, a health check function can be created based on time trigger which will keep the func app not needed a cold start.
Upvotes: 0
Reputation: 625
It's been a long time since I have a similar problem, but what worked for me when some function went to sleep was:
I don't really know why sometimes some functions goes idle and then it no longer trigger.
Upvotes: 0