This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 53%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
hi. I have some question about the Azure Function. I made a Azure Function(http trigger). But someday the error of [Singleton lock] happend. The error log look like this: Singleton lock renewal failed for blob 'XXXXX/host' with error code 409: LeaseIdMismatchWithLeaseOperation. The last successful renewal completed at 2021-03-07T16:48:04.053Z (31246 milliseconds ago) with a duration of 4 milliseconds. The lease period was 15000 milliseconds. I checked the Azure Function's [Metrics]. The [Function Execution Count] is 0 when this error happend. That means This error has nothing to do with my function itself. I want to know: 1,What happens in a factor? 2,How does it affect? 3,Do you have a solution? Thanks.
@潘宇 Could you confirm if you have any other functions in the same function app? AFAIK HTTP trigger doesn't really depend on storage leases in anyway. It is likely that you have a Timer trigger function alongside this HTTP function.
Thanks.
But I have checked this function.
There is no timer trigger in this function.
@潘宇 A function can have only one trigger. Could you confirm if you have other functions in the same app?
Thank you for your opinion.
I confired my function app.
There are three functions in My Function App.
(I can see them in the menu [Functions].)
One is [HTTP].
One is [Activity].
One is [Orchestration].
In the source code, we call by http trigger.
In this http trigger function, we call the Orchestration.
In this Orchestration function, we call the Activity.
And there did not have any other function in this function app.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 90%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKI%3C/text%3E%3C/svg%3E)
I'm in the process of testing a proof of concept to provide CSV file processing using durable functions. I've thrown them in with our other HTTP functions. Processing a smaller file was fine, but I get this error for a large file. Do you know why this happens? are you certain it's due to being along side http function?
Many thanks
Ian
@Klek, Ian It is possible the processing of the large CSV is taking up all available resources causing the renewal to not happen in time. But as mentioned in the answer here, this shouldn't be a problem.
@潘宇 Looks like this exact error is being discussed in this issue and based on this comment it isn't a problem. There are a couple of instances where this log is recorded but the lease should be reacquired after a bit.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 87%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPP%3C/text%3E%3C/svg%3E)
@Pramod Valavala Was this issues resolved? I am getting similar failure error with my function app also it has a Get HTTP Trigger method
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 84%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWT%3C/text%3E%3C/svg%3E)
I have a similar issue, the Orchestrator was triggered by HTTP Trigger, and normally the orchestrator can be finished in less than 10mins, while when hit the 409 issues will process more than 2 hours or 2 days, does anyone have an idea why hit 409? on this?