---
title: "Comment by Bogdan Mihai Cosofret on \"Exponential retry with Azure Function and Service Bus trigger\" | Hashnode"
description: "I would add something to this. Because you are not throwing any exceptions in the function, then in the function monitoring you'll see only green runs, as i"
url: "https://hashnode.com/posts/exponential-retry-with-azure-function-and-service-bus-trigger/6322edf68350c8888bf306c3/comment/651e7d9c11a36fafb910f6cc"
---

[Discussion](https://hashnode.com/posts/exponential-retry-with-azure-function-and-service-bus-trigger/6322edf68350c8888bf306c3)

Comment [Exponential retry with Azure Function and Service Bus trigger](https://hashnode.com/posts/exponential-retry-with-azure-function-and-service-bus-trigger/6322edf68350c8888bf306c3)

[Oct 5, 2023](https://hashnode.com/posts/exponential-retry-with-azure-function-and-service-bus-trigger/6322edf68350c8888bf306c3/comment/651e7d9c11a36fafb910f6cc)

I would add something to this. Because you are not throwing any exceptions in the function, then in the function monitoring you'll see only green runs, as if the function has succeeded every time when in fact it failed.

I used a solution very similar to this, but on retries, after completing the received message and sending a new one to the service bus, I threw the caught exception at the end. If you do this, then the function runs will appear as failed in the monitor.