Retry policies for isolated (out-of-process) AF Cosmos DB triggers/bindings soon deprecated?

@kshyju answer below works at the moment, but now we recently started to see the following trace in AppInsights for our AF Cosmos DB triggers : “Soon retries will not be supported for function ‘[Function Name]’. For more information, please visit http://aka.ms/func-retry-policies.”

The Retry examples section also shows “Retry policies aren’t yet supported when running in an isolated process.” and the Retries section reflects no support for the Cosmos DB trigger/binding.

What’s the path forward for AF Cosmos DB triggers running out-of-process?

Yes, retry policies are supported in isolated(out-of-process) function apps. You can enable it by adding the retry section to your host config. Here is an example host.json

{
  "version": "2.0",
  "retry": {
    "strategy": "fixedDelay",
    "maxRetryCount": 2,
    "delayInterval": "00:00:03"
  }
}

The reason why I’m asking is the documentation mentioning Retries require NuGet package Microsoft.Azure.WebJobs >= 3.0.23

That documentation which refers the usage of ExponentialBackoffRetry attribute is for in-proc function apps.

Please give it a try and let us know if you run into any problems.

_Originally posted by @kshyju in https://github.com/Azure/azure-functions-dotnet-worker/issues/832#issuecomment-1072545934_

[MikeNicholls]

Will there be any guidance on retries for Cosmos DB triggered functions before the October 2022 deadline when retry policy support will be removed?

Cosmos DB is currently the outlier on the table of retry support for triggers/bindings, with “n/a” and “Not configurable” listed. https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-error-pages#retries

[ealsur]

@sayyaari The change I added is for the 4.x extension that will release sometime next month, the document would need to be updated I guess