Re-test your campaign flows in Winter '27's new Flow Test Mode
Winter '27 replaces Flow Debug Mode with a dedicated Test Mode and adds Flow Tags. Re-run every live campaign flow this week and tag the ones that send.
Winter '27, generally available from 12 October 2026, gives Flow Builder a dedicated Test Mode in place of Debug Mode, and adds Flow Tags for organising and finding flows. Both are platform changes, so they apply to every Marketing Cloud Next campaign flow, segment flow and consent flow as much as to sales automation. The same release also lets screen flows process several records from a list view.
- Product
- Marketing Cloud Next
- Edition
- edition not stated in the source
- Topic
- Flow for marketers
- Last verified
Who this applies to
- Admins and marketers who maintain campaign, segment and consent flows in Marketing Cloud Next
- Orgs with more than a handful of marketing flows and no naming convention
- Edition: not stated; Flow Builder changes apply across editions
Why it matters
A release upgrade is the one moment every flow in the org runs on a new engine at once. The flows most teams forget to re-test are the quiet ones: the consent flow that opts a lead in, the single-purpose notification flow, the segment flow nobody has opened since it was built. Test Mode makes a run cheap to do and easy to read; Flow Tags make it possible to find all the marketing flows in the first place.
Try it
- Tag every active marketing flow with one tag per purpose: send, consent, segment, notify. Do it from the flow list before you test anything, so the list is the test plan.
- Open each flow tagged send or consent in Test Mode and run it with one real-shaped record. Read the path it took, not just the outcome; a wait that resolved differently is still a change.
- For flows with a Personalize Paths or Path Experiment element, run one record per path.
- Record which flows you tested and the date in the flow description, so the next release does not start from zero.
- Fix or deactivate anything that behaved differently before the first post-upgrade campaign send; do not let a live send be the test.
Example use case
A team with forty marketing flows tags them in an hour, finds six that nobody owns, and re-tests the nine that send or write consent. One consent flow that worked on Summer '26 now needs a field mapping corrected; it is fixed before the week's newsletter rather than discovered in the Email Send Outcomes report.
Prerequisites, limitations and risks
- Winter '27 in the org (production from 12 October 2026; preview sandboxes from late August)
- A sandbox to test in; Test Mode runs in production too, but sends and consent writes are real there
- Permission to edit flows and to see the flow list for the marketing app
Documented behaviour above comes from the sources listed below. Availability varies by edition, SKU and region - confirm entitlements in your own org before you rely on a feature.
Sources
- Salesforce Winter '27 Release Notes (hub)
- Salesforce Winter '27 Release: Everything You Need to Know Before Go-Live Community
Stuck on this in your own org?
Blueport is a Sydney-based Certified Salesforce Consulting Partner with 100+ implementations since 2018. If a step above does not match what you see in Marketing Cloud Next, tell us - it is either an edition difference or a change worth knowing about, and we will find out which.
Talk to our team