From bbc4328453dc887fbe507364a2e032c6e5b184e7 Mon Sep 17 00:00:00 2001 From: Nitish Agarwal Date: Thu, 9 Jul 2026 09:12:48 +0530 Subject: [PATCH] Add SUGGEST_CONTINUE_AS_NEW_REASON_TOO_MANY_SIGNALS enum value Add a new SuggestContinueAsNewReason value so the server can advise a workflow to continue-as-new when its signal count approaches maximumSignalsPerExecution, before the hard ErrSignalsLimitExceeded rejection. This is the signals analog of the existing TOO_MANY_UPDATES reason. --- temporal/api/enums/v1/workflow.proto | 3 +++ 1 file changed, 3 insertions(+) diff --git a/temporal/api/enums/v1/workflow.proto b/temporal/api/enums/v1/workflow.proto index a9ac3fc33..118e743f2 100644 --- a/temporal/api/enums/v1/workflow.proto +++ b/temporal/api/enums/v1/workflow.proto @@ -222,4 +222,7 @@ enum SuggestContinueAsNewReason { // See target_worker_deployment_version_changed to find out if Target Version Changed. reserved 4; reserved "SUGGEST_CONTINUE_AS_NEW_REASON_TARGET_WORKER_DEPLOYMENT_VERSION_CHANGED"; + + // Workflow's signal count is approaching the configured maximum signals per execution. + SUGGEST_CONTINUE_AS_NEW_REASON_TOO_MANY_SIGNALS = 5; }