Azure / Azure/azure-functions-dotnet-worker
CosmosDBtrigger retry policy will be removed in isolated mode?
- Dominant language
- C#
- Stars
- 466
- Forks
- 215
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 7
Description
Our services are using CosmosDBTrigger heavily. We are currently using in-process mode and are going to migrate to isolated mode. But seeing from this doc: https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-error-pages?tabs=fixed-delay%2Cisolated-process&pivots=programming-language-csharp#retry-policiesretry-policies
The retry policy will be removed in the future.
Since now we have many place using attributes like[FixedDelayRetry] and [ExponentialBackoffRetry], will this also not support in the future? If it is, do we have any alternative ways (which is similar to attributes or json configure retry policy) for retry exception for CosmosDBTrigger to avoid the breaking change?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.