Allow client to specify retry next interval

temporal/api/workflowservice/v1/request_response.proto

@@ -492,6 +492,14 @@ message RespondActivityTaskCompletedByIdRequest {
 message RespondActivityTaskCompletedByIdResponse {
 }
 
+message ActivityOverride {
+    // 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 = 1;
+}
+
 message RespondActivityTaskFailedRequest {
     // The task token as received in `PollActivityTaskQueueResponse`
     bytes task_token = 1;
@@ -506,6 +514,9 @@ 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;
+    // Allow activity to influence decisions made by the server when processing this request
+    // with regards to this activity only
+    ActivityOverride overrides = 7;
 }
 
 message RespondActivityTaskFailedResponse {
@@ -529,6 +540,9 @@ message RespondActivityTaskFailedByIdRequest {
     string identity = 6;
     // Additional details to be stored as last activity heartbeat
     temporal.api.common.v1.Payloads last_heartbeat_details = 7;
+    // Allow activity to influence decisions made by the server when processing this request
+    // with regards to this activity only
+    ActivityOverride overrides = 8;
 }
 
 message RespondActivityTaskFailedByIdResponse {