Alternative for Retry Policies due to "Soon retries will not be supported for function 'xxx'" warning

Craig McLellen 26 Reputation points
2022-08-05T05:21:34.063+00:00

Hi,

We're using a ServiceBusTrigger in our Azure Function App with the ExponentialBackoffRetry attribute defined. I've noticed the warning "Soon retries will not be supported for function 'xxx'. For more information, please visit http://aka.ms/func-retry-policies." in our logs and looking at the provided link, the documentation mentions

The retry policy support in the runtime for triggers other than Timer and Event Hubs is being removed after this feature becomes generally available (GA). Preview retry policy support for all triggers other than Timer and Event Hubs will be removed in October 2022.

It's not clear what the alternative solution to this is - is there one? We need this capability, otherwise on dependent service restarts, our DLQs will be flooded.

Eagerly looking forward to a solution. Thank you

Azure Service Bus
Azure Service Bus
An Azure service that provides cloud messaging as a service and hybrid integration.
662 questions
Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,399 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Stefano Demiliani 166 Reputation points MVP
    2022-08-05T07:39:24.76+00:00

    As stated in this link:
    https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus?tabs=in-process%2Cextensionv5%2Cextensionv3&pivots=programming-language-csharp
    I think that you should use bindings:
    https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus?tabs=in-process%2Cextensionv5%2Cextensionv3&pivots=programming-language-csharp
    so in your host.json file using the clientRetryOptions configuration:
    {
    "version": "2.0",
    "extensions": {
    "serviceBus": {
    "clientRetryOptions":{
    "mode": "exponential",
    "tryTimeout": "00:01:00",
    "delay": "00:00:00.80",
    "maxDelay": "00:01:00",
    "maxRetries": 3
    },
    "prefetchCount": 0,
    "transportType": "amqpWebSockets",
    "webProxy": "https://proxyserver:8080",
    "autoCompleteMessages": true,
    "maxAutoLockRenewalDuration": "00:05:00",
    "maxConcurrentCalls": 16,
    "maxConcurrentSessions": 8,
    "maxMessageBatchSize": 1000,
    "sessionIdleTimeout": "00:01:00",
    "enableCrossEntityTransactions": false
    }
    }
    }

    1 person found this answer helpful.

  2. Sanja Stojkova 16 Reputation points
    2022-12-06T08:34:44.263+00:00

    Hi @Craig Muckleston what happened? Any update? I am facing the same issue. Thank you

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.