Can't run TimerTrigger Azure Function

Question

Hello! I am a new guy in the Azure field and I've created a free Azure account so I can play around with the services. I've created a HttpTrigger function and it worked fine, but when I've tried creating a TimerTrigger function, it just doesn't work. I've tried multiple times creating this type of function by deleting and creating a new one but I still couldn't get it to work. The error is :
Could not create BlobContainerClient for ScheduleMonitor

I've searched online to see if other people encountered this issue but couldn't find anything. The thing is that I'm creating this function from the portal using .NET and I don't change the file.csx or the function.json files. I don't even touch them, I just create the function and hit the Test/Run button.
As I've said before, I have a free Azure account and when I open the FunctionApp resource I get this warning message:
Storage is not configurand properly. Function scaling will be limited

I don't really know why this message pops us, I have a storage account that's linked to the resource grup where the FunctionApp is also. When I've followed tutorials on the internet, the teachers there just created the function as I do and it worked for them. I also don't have any logs in the monitor tab from the function that doesn't work.

Please help me solve this problem so I can start learning about Azure Functions!

Answer 1

Hi @Steelu ,

Thank you for reaching out to Q&A forum and welcome to Azure Functions!

The Function app uses the Storage account for logging and storing the source code. Also the function keys are present in the Storage containers. If you look at the storage account associated with the function app, you would containers called "azure-webjobs-hosts" and "azure-webjobs-secrets". The timer trigger uses the storage account to read the cron schedule from a file called status inside the "azure-webjobs-hosts" container, when this file is not reachable/ not present, then you would see the message "Could not create BlobContainerClient for ScheduleMonitor".

You are also seeing "Storage is not configurand properly. Function scaling will be limited" message in the portal which means this is the main reason why the timer is also failing. It appears that the Storage account is either deleted or not properly configured. Please look into this article to resolve the Storage issue.

Feel free to reach out to me if you have any questions or concerns.