From 3384ea5f3296186163e3fee14fb98633c86d67a6 Mon Sep 17 00:00:00 2001
From: sasha <alex.shafir@temporal.io>
Date: Thu, 7 Dec 2023 13:02:33 -0800
Subject: [PATCH] Allow client to specify retry next interval

---
 temporal/api/workflowservice/v1/request_response.proto | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/temporal/api/workflowservice/v1/request_response.proto b/temporal/api/workflowservice/v1/request_response.proto
index 0785ae07..90b122a9 100644
--- a/temporal/api/workflowservice/v1/request_response.proto
+++ b/temporal/api/workflowservice/v1/request_response.proto
@@ -506,6 +506,11 @@ message RespondActivityTaskFailedRequest {
     // always be set by SDKs. Workers opting into versioning will also set the `use_versioning`
     // field to true. See message docstrings for more.
     temporal.api.common.v1.WorkerVersionStamp worker_version = 6;
+    // next_retry_delay can be used by the client to override the activity
+    // retry interval calculated by the retry policy. Retry attempts will
+    // still be subject to the maximum retries limit and total time limit
+    // defined by the policy.
+    google.protobuf.Duration next_retry_delay = 7;
 }
 
 message RespondActivityTaskFailedResponse {