Verge 4.2.0: scheduled sends survive a restart
Verge, a launch email, finished in HTML.
A version number set on the editor it came out of, three tagged entries with hairlines between them, and a support window at the end. For shipping a version of a developer product.
Read the email as text
VERGE
RELEASE NOTES // 11 SEPTEMBER 2026
v4.2.0
One breaking change, one fix worth upgrading for, and a flag we should have shipped a year ago.
Released
11 Sep
Breaking
1
Upgrade
~10 min
Breaking
POST /sends rejects an empty recipient list
It used to return 202 and quietly do nothing, which meant a broken segment looked like a successful send in your logs. It now returns 422 with the code recipient_list_empty. If you were relying on the no-op, check the array length before you call.
Fixed
A send resumes after the worker running it restarts
A send that was in flight when a worker died stalled at whatever batch it had reached, and stayed there until somebody noticed. The queue now checkpoints every 500 recipients and resumes from the last one it confirmed. Nobody gets the same email twice.
Added
A dry_run flag on the send endpoint
Pass it and the API validates the payload, renders the first recipient and returns the HTML, without sending anything or touching your quota. We added it because we kept testing against real inboxes, which is a bad habit we would rather you did not learn from us.
4.1.x keeps getting security fixes until 31 March 2027. The upgrade guide covers the recipient list change in more detail.
Verge · Sent to everyone with an API key Change what you hear about in your notification settings. Unsubscribe · View in browser
