[Wf-Diagnostics] update troubleshooting guide for blob size limits (#203

) * [Wf-Diagnostics] update troubleshooting guide for blob size limits * Update src/docs/08-workflow-troubleshooting/02-activity-failures.md Co-authored-by: Jakob Haahr Taankvist <[email protected]> * Update src/docs/08-workflow-troubleshooting/02-activity-failures.md Co-authored-by: Jakob Haahr Taankvist <[email protected]> * Update 02-activity-failures.md --------- Co-authored-by: Jakob Haahr Taankvist <[email protected]>
cadence-workflow · Jan 3, 2025 · b792f3b · b792f3b
1 parent 000c888
commit b792f3b
Showing 1 changed file with 14 additions and 0 deletions.
diff --git a/src/docs/08-workflow-troubleshooting/02-activity-failures.md b/src/docs/08-workflow-troubleshooting/02-activity-failures.md
@@ -25,3 +25,17 @@ Mitigation: This error is caused by something unexpected within the activity cod
 
 Read more about [error handling](https://cadenceworkflow.io/docs/go-client/error-handling/)
 
+## Blob Size limits
+Description: This is an error caused when a decision contains data that exceeds the configured limit. If an API call contains data that exceeds the limit, the API call will fail. These limits are dynamically configured per cadence domain [link to code](https://github.com/cadence-workflow/cadence/blob/master/common/dynamicconfig/constants.go#L2938).
+
+Mitigation: It is recommended to store the data elsewhere in another storage technology and using its reference. The workflow can then take that reference and pass it around to other parts of the workflow to retrieve that data.
+
+Cadence enforces the maximum blob size in several cases. Some of these are:
+
+- Signal input
+- Workflow input and output
+- Workflow continueAsNew input
+- Activity input and output
+- Workflow/Activity error_details
+- Record marker
+- Heartbeat details