You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 449174b
Browse filesBrowse the repository at this point in the historyBrowse files
fix(api): pause the send on a permanent render error instead of dropping recipients
Counting render failures per recipient meant a team-wide problem (an empty
mailing address, or a footer render bug like #154) unenrolled every recipient
within minutes. Content and footer errors (EmailRenderError,
TemplateValidationError, Liquid syntax errors) now auto-pause the broadcast or
sequence with a new `render_error` reason: the team is notified, everyone
stays queued, and resuming sends to all of them. Other errors while rendering
are transient and are retried without counting. The send-failure path is back
to exactly what it was on main.
The pause banner and the owner email explain the reason in words, and
SequenceReport.autoPause.reason in @sendlit/email-blocks gains `render_error`.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
`SequenceReport.autoPause.reason` can now be `render_error`: SendLit paused a broadcast or sequence because its email couldn't be built (for example the managed footer or the mailing address), keeping its recipients queued until it is resumed.
0 commit comments