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(211.20000000000002, 51%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBT%3C/text%3E%3C/svg%3E)
I have a simple question about how queue-triggered azure functions manage message visibility in the event that the function run for a long time.
I understand that with peek-lock, a queue-triggered function will temporarily make the message invisible to other consumers. If the function succeeds, the message is removed from the queue. If it fails (or if the host crashes) the message will be returned to the queue to be retried.
I can see that when a message is picked up by the queue triggered function, it has a visibility timeout of 10 minutes in the future. What will happen if the function instance runs for longer than 10 minutes? Is there a background process which updates the visibility timeout automatically, keeping the message invisible to other consumers as long as the process is healthy?
I could not find any documentation which explicitly mentioned this, but based on my experimentation it seems to be the case. Wanted to ask here and see if this behavior is confirmed.
![](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(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
there is no background update of the timeout, it is set when the item is dequeued. if your process runs long, it should update the dequeued items visibility timeout, just like it should delete when done.
![](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(57.599999999999994, 5%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPK%3C/text%3E%3C/svg%3E)
Hello Bradley Treuherz,
The Azure Functions runtime automatically extends the visibility timeout of queue-triggered messages while the function execution is in progress.
If your function runs longer than the default 10-minute visibility timeout, the runtime periodically renews the lease in the background, keeping the message invisible to other consumers.
This behavior ensures reliable processing and prevents duplicate execution as long as the function host remains healthy.
Hello Bradley Treuherz,
If this answer was helpful, please click "Accept the answer" and mark Yes, as this can help other community members.
If you have any other questions or are still experiencing issues, feel free to ask in the "comments" section, and I'd be happy to help.