Skip to content

Commit 95014cd

Browse files
authored
Update docs/troubleshooting/blob-size-limit-error.mdx
1 parent e1ccc38 commit 95014cd

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/troubleshooting/blob-size-limit-error.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Workflow is not terminated and remains open, so you can deploy a fix and allow t
6363
This is called the
6464
[claim check pattern](https://dataengineering.wiki/Concepts/Software+Engineering/Claim+Check+Pattern). The claim
6565
check pattern is built into the SDKs as [External Storage](/external-storage), or you can implement your own claim
66-
check pattern by using a custom [Payload Codec](/paload-codec)
66+
check pattern by using a custom [Payload Codec](/payload-codec)
6767

6868
This is the most reliable way to avoid hitting payload size limits. Consider implementing the claim check pattern for
6969
Workflows and Activities that have the potential to receive or return large payloads, even if they are currently

0 commit comments

Comments
 (0)