Warn against base64 images in email editors (DOC-2307) - #461
Open
BrindaaRC wants to merge 1 commit into
Open
Conversation
Add warnings to the drag-and-drop and custom HTML editor docs advising users to upload images or use a hosted URL instead of pasting large base64-encoded image data into link/URL fields or HTML. A large base64 payload can exceed the message-size limit during the async send and cause the campaign to fail silently with a Sent count of 0. Addresses DOC-2307 (source SUP-8422). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changed
Adds warnings to both email editor docs advising users to upload images (or reference a hosted image URL) instead of pasting large base64-encoded image data into link/URL fields or HTML.
<Warning>in the "How to Upload Files?" section.<Warning>in the "Add HTML Code" section.Why
Support ticket SUP-8422: a client pasted a ~700 KB base64-encoded image directly into a link/URL field. The oversized payload exceeded the message-size limit during the async send, so the campaign failed to send (Sent count 0) with no clear error. The behavior is engineering-confirmed.
Reviewer notes
🤖 Generated with Claude Code