From c30f2087660e1a7079d21e148ba67b19ff13b1a7 Mon Sep 17 00:00:00 2001
From: jmaeagle99 <44687433+jmaeagle99@users.noreply.github.com>
Date: Tue, 10 Feb 2026 12:07:02 -0800
Subject: [PATCH] Update TMPRL1103 with more information

---
 rules/TMPRL1103.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/rules/TMPRL1103.md b/rules/TMPRL1103.md
index c922e5f..3c04aec 100644
--- a/rules/TMPRL1103.md
+++ b/rules/TMPRL1103.md
@@ -6,4 +6,14 @@ The size of a payload or collection of payloads has exceed configured size limit
 
 ## Description
 
+By default, the SDK will check the size of payloads as they move throughout workflows, activities, and Nexus operations. The SDK will log warnings if the size of the payloads are over the warning limit and throw exceptions or return errors if they are over the error limit.
+
+The error limit is only enforced within workers when attempting to submit messages to the Temporal server and they exceed the error limits as described by the server. When the error limit is exceeded, the worker task is proactively failed instead of sending the large payload to the server. This helps the server to prevent excessive resource usage and avoid potential performance issues when handling large payloads. Additionally, failing the task allows the task to be retried instead of failing the associated workflow.
+
 ## Remediation
+
+To resolve this error, reduce the size of the payload so that it is below the error limit.
+
+Refer to https://docs.temporal.io/troubleshooting/blob-size-limit-error for further information about payload error limits and strategies to reduce payload sizes.
+
+Customers who use gRPC proxies that alter payloads before they are passed to the server (e.g. encrypting payloads, offloading to external storage, etc) should disable the error limit check in their workers. Please refer to the worker option documentation for the SDK on how to disable this behavior.
\ No newline at end of file