You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our services are using CosmosDBTrigger in isolated mode and are relying on attributes like [FixedDelayRetry] and [ExponentialBackoffRetry] for retry on exception.
Is it possible the let the CosmosDBTrigger do infinitely retry on exception during the execution? like setting the retry count to -1?
The text was updated successfully, but these errors were encountered:
@blankor1 it sounds like you want high levels of resilience for this trigger. If that is the case, I don't recommend relying on retries as many other external factors may lead to even that not being a guarantee (instance crash, scale in, shutdown, etc). Additionally, sometimes there is a fatal error where no matter how many times your trigger retries it will never succeed (did you delete the resource / db / container? lose access? ETag issues?)
For resilience, I recommend looking into durable functions. This will be much more reliable for a distributed application, as it can retry between crashes, restarts, etc.
But to answer your question directly: retry attributes are just a convenience method. If they do not suit your needs (such as indefinite retry), you can look into using something like Polly directly in your trigger.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
If you are not the original author (blankor1) and believe this issue is not stale, please comment with /bot not-stale and I will not close it.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
Our services are using CosmosDBTrigger in isolated mode and are relying on attributes like [FixedDelayRetry] and [ExponentialBackoffRetry] for retry on exception.
Is it possible the let the CosmosDBTrigger do infinitely retry on exception during the execution? like setting the retry count to -1?
The text was updated successfully, but these errors were encountered: