Vova Bilyachat
Vova Bilyachat

Reputation: 19514

Azure webjob max execution time or Blob queue max lock retry

In my project i have Webjob which is triggered by queue. Its sending newsletter and its time consuming i can say exactly how long it takes but more than 10 minutes.

Logic to update release lock every 25 seconds

queue.UpdateMessage(data, TimeSpan.FromSeconds(60.0), MessageUpdateFields.Visibility);

Everything works as expected till today when it just failed with message Never Finished 57 minutes ago and i see that same message was queued 3 times.

I've added logging to see why, but it will take probably few days till next newsletter. So maybe somebody know about recent changes or limits?

Upvotes: 0

Views: 1334

Answers (1)

Brando Zhang
Brando Zhang

Reputation: 28372

Azure webjob max execution time

As far as I know, azure web job doesn't have the max execution time.

Here is a test, the webjob execute 30 minutes.

enter image description here

Blob queue max lock retry

I couldn't understand why you release lock of the queue message which the web job method currently used.

If a web job is triggered by one queue message, it will be invisible until the method fail or complete.

Azure web job SDK will call a function up to 5 times to process a queue message. If the fifth try fails, the message is moved to a poison queue.

The poison queue name is {originalqueuename}-poison.

About how to set the maximum number of retries, you could refer to this article.


Update:

enter image description here

Upvotes: 1

Related Questions