Azure timer trigger function hangs for a few minutes and then resumes
Hello everyone,
I have to ask if anyone has any experience with a situation where a timer trigger function just hangs for some reason and then resumes after a few minutes (could be 2-3 minutes, could be up to 8).
I have a function app with a consumption plan and one function in it, which is a timer trigger function, that’s supposed to fetch some items through graphAPI and load them into the storage account queue.
Everything works well, but everytime it runs (every 10 minutes) it just freezes at some point just to resume after a few minutes.
I had to extend the functionTimeout value to 10 minutes, because prior to that it would just hang and the function would timeout. Now it’s at least able to do some processing before the timeout happens.
Here is a picture of from app insights of the last print before the hang:
And now the picture of a first print after if resumes:
As you can see, there is no error, traceback, anything. Also the hang happens quite early after the start (usually within the first 20s) and at a random point, so I couldn’t narrow it down to a faulty code.
I think the is some issue with the resources, host lock lease or any underlying architecture, but I don’t know where to look.
I’d gladly accept any advice or any new lead that I could chase.
Thanks!
Hello everyone, I have to ask if anyone has any experience with a situation where a timer trigger function just hangs for some reason and then resumes after a few minutes (could be 2-3 minutes, could be up to 8). I have a function app with a consumption plan and one function in it, which is a timer trigger function, that’s supposed to fetch some items through graphAPI and load them into the storage account queue.Everything works well, but everytime it runs (every 10 minutes) it just freezes at some point just to resume after a few minutes.I had to extend the functionTimeout value to 10 minutes, because prior to that it would just hang and the function would timeout. Now it’s at least able to do some processing before the timeout happens. Here is a picture of from app insights of the last print before the hang:And now the picture of a first print after if resumes:As you can see, there is no error, traceback, anything. Also the hang happens quite early after the start (usually within the first 20s) and at a random point, so I couldn’t narrow it down to a faulty code. I think the is some issue with the resources, host lock lease or any underlying architecture, but I don’t know where to look. I’d gladly accept any advice or any new lead that I could chase. Thanks! Read More