Emit GrpcMessageTooLarge as failure_reason for WFT #1069
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the workflow task failure is due to gRPC message too large, set GrpcMessageTooLarge as
failure_reasonontemporal_workflow_task_execution_failed.closes #1065
Note
Adds a specific failure_reason label GrpcMessageTooLarge to workflow task failure metrics when WFT completion hits an oversized gRPC message and records the metric.
FailureReason::GrpcMessageTooLargeand support emittingfailure_reasonviametrics::failure_reason(...).metrics: MetricsContextinWorkflowsand, oncomplete_workflow_taskerror flaggedMESSAGE_TOO_LARGE_KEY, fail the WFT withGrpcMessageTooLargecause and recordwf_task_failedwithfailure_reason="GrpcMessageTooLarge".oversize_grpc_messageintegration test to enable Prometheus and assert thetemporal_workflow_task_execution_failedmetric includesfailure_reason="GrpcMessageTooLarge".Written by Cursor Bugbot for commit cdf0c95. This will update automatically on new commits. Configure here.