Dapr resiliency policy for retries not working as expected

Sandeep Chandra 0

I have a subscription with resiliency policy defined for Dapr as shown in the screenshot. The issue I have is that the retries happen all at once without any delays, and then the message is DLQed. Have I got something wrong in this config?

Khadeer Ali 3,670 Reputation points Microsoft Vendor

2024-12-03T05:46:49.95+00:00

Hi Sandeep Chandra,

Just following up to check if the issue still persists!
Sandeep Chandra 0 Reputation points

2024-12-03T09:00:09.8133333+00:00

Hi Khadeer

I have done the changes in prod env, will keep an eye for a while and let you know if I see it again.
Sandeep Chandra 0 Reputation points

2025-02-06T00:47:12.66+00:00

Hi Khadeer

I am still seeing the retires not delayed as per the resiliency policy in the screenshot

The reties as per logs are only a minute apart as shown below. I need them to be at least an hour apart. Also, I was expecting the number of retries to be 168 which is not the case.

I suspect there is an issue with Dapr here.

Regards

Sandeep
Sandeep Chandra 0 Reputation points

2025-02-21T07:23:15.5+00:00

Is anyone still monitoring this thread? I have had this issue again.
Khadeer Ali 3,670 Reputation points Microsoft Vendor

2025-02-21T15:17:09.59+00:00

@Sandeep Chandra ,

I appreciate your follow-up on this. I had shared my response with the debugging steps over a private message earlier. Could you please check there and let me know if you have any further questions? Happy to assist!

1 answer

Khadeer Ali 3,670 Reputation points Microsoft Vendor

2024-12-02T02:12:48.8433333+00:00

Hi Sandeep Chandra,

Welcome to the Microsoft Q&A Platform! Thank you for reaching out regarding your query on Dapr Resiliency Policy.

The issue here might lie in the large initial delay. Since the first retry is delayed by an hour, subsequent retries might happen in quick succession after the initial delay. This can result in a burst of retries, potentially overwhelming the target system and causing DLQing.

Could you try reducing the initial delay to a smaller value? This would ensure that retries begin sooner and are more evenly spaced out.
Please sign in to rate this answer.
Sandeep Chandra 0 Reputation points

2024-12-02T08:52:14.93+00:00

Hi Khadeer,

I have reduced the initial delay as shown in the screenshot, will update of the outcome here.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Dapr resiliency policy for retries not working as expected

1 answer

Your answer