Alert This post is over a year old, some of this information may be out of date.

How to let an Azure Function know something failed

May 18, 2017

Just a quick article about how you can let your Azure Function runtime know there was a problem during the execution. This is important when you are for example working with queue triggered functions.

The default method to let your Azure Function know it has finished is the context.done() method. When you use the method like this: context.done(), the runtime thinks everything was executed correctly. In the case of working with Azure storage queues, the actually processed message gets automatically removed. Which is, of course, unwanted behavior when something failed.

While I was reading through the Azure Functions Node.js reference documentation, I noticed that the first parameter you can pass to the context.done method is an error. Once you use it, the Azure Function is informed that there was a problem, and in the case of working with queues, it does not remove the message. The good thing is, the Azure Function will automatically retry 5 times before sending the message to a poison queue.

Info: Azure Functions JavaScript developer guide -

Here is an example of how you can use it:

module.exports = function (context, myQueueItem) {
  context.log(`Start with the following message: "${myQueueItem}"`);
  context.log(`Dequeue count: ${context.bindingData.dequeueCount}`);
  context.done("Something failed");

This is the output of the function:

Log output of the sample code
Log output of the sample code

As you can see in the above screenshot, the function gets triggered 5 times before it gets sent to a poison queue. When you would remove the error parameter, it will only be processed once. Throwing errors also result in the same outcome (one time processed).


comments powered by Disqus