Automations Built to Run for Months

​

What Shipped

Lifecycle programs keep getting longer: 90-day onboarding, renewal reminders months out, win-backs after half a year. This release is for those. Set an automation up once and it keeps running, however long its waits are.

​

Every Step Runs on the Latest Brew

Each step of an automation now runs on the current version of Brew, not the one that enrolled the contact. A contact 60 days into a series gets today’s rendering and deliverability checks on their next email. Waits of 30, 60, or 180 days continue exactly where they left off.

​

Contacts in Flight Keep Moving

Brew watches every contact moving through an automation. If one stops, on a wait, after a send, or between steps, Brew continues them from that point. A contact who can’t continue shows the reason on the run.

​

Retry Resumes Where a Run Stopped

Retry continues from where the run stopped and skips every email the contact already received. If Brew can’t confirm an email went out, it stops at that step and tells you. Each run can be retried once, so a second click or a teammate in another tab won’t start a duplicate.

​

Schedule Up to a Year Ahead

A scheduled campaign or automation run can start up to a year out, and starts on time on the latest Brew. See Send Options.

​

Analytics Keep Every Step

On an automation’s analytics page, Email steps now include steps you’ve since removed. They keep their sends, opens, and clicks under a Removed step label, so a redesign doesn’t erase the history you’re comparing against. Automations you’ve unpublished keep their step numbers too.

​

Test Emails Go to Your Team

Test sends now go to you, anyone at your company’s domain, a teammate with access to the brand, or an address on one of the brand’s verified sending domains. Drafts stay inside your company until you send them for real. Other addresses are refused, and Brew names them. Sends to your audience aren’t affected. From an agent or code, the rule covers test: true on POST /v1/sends and automation test sends. An API key can reach teammates and verified sending domains. A refused address returns 422 TEST_RECIPIENT_NOT_ALLOWED.

​

Get Started

Open any automation and choose Runs to see each contact’s progress. Automations covers runs and retries.