Version history for flows
Klaviyo flows keep a version history: users can restore an earlier version, see who changed what, and copy a past version into a draft, including Composer's changes.
Entries on this page are generated by AI from vendor sources. How AI is used
Multi-step, stateful customer journeys on a canvas.
| Month | Changes |
|---|---|
| 2026-01 | 9 |
| 2026-02 | 5 |
| 2026-03 | 13 |
| 2026-04 | 8 |
| 2026-05 | 6 |
| 2026-06 | 14 |
| 2026-07 | 6 |
| 2026-08 | 7 |
| 2026-09 | 23 |
| 2026-10 | 11 |
| 2026-11 | 1 |
Select a month to view the whole-record timeline. This clears timeline filters.
Platforms with at least one feature state classified in this capability (primary or secondary, minor updates included), in the site's fixed order. Select one to filter the timeline. Counts are not shown side by side: they reflect how finely each vendor documents, not how much it offers.
Filters apply to the timeline. The chart and platform totals describe the whole record. Selecting a chart month clears timeline filters to show that same whole-record scope.
Matches the Release Matrix evidence: latest state reached in the selected period, entries under review excluded, primary and secondary capabilities included.
No recorded changes match these filters.
Within each period: major updates as cards, then notable ones as rows; newest first in each group. Minor updates below.
Klaviyo flows keep a version history: users can restore an earlier version, see who changed what, and copy a past version into a draft, including Composer's changes.
Five journey alerts, in limited availability, flag message bounce and delivery-error rates and event delays from exceeded throughput guardrails, plus Read Audience export start/complete notifications.
The journey canvas offers a Loop tile that sends users back through a journey section for a limited number of repeats, with criteria for when to loop or exit.
Flows can add a Customer Hub content block action that surfaces the flow's message as content in each shopper's For You tab on the website.
A Stop action activity in the journey canvas removes a profile from up to five inbound activities or experiences, decoupling inbound disqualification from journey exit.
A Validate button runs configuration and message checks on demand when testing or publishing a journey, instead of continuously during editing.
Now Preview (29 Oct 2026). Current summary: Five journey alerts, in limited availability, flag message bounce and delivery-error rates and event delays from exceeded throughput guardrails, plus Read Audience export start/complete notifications.
An AI agent panel beside the journey canvas sees the open journey including unsaved edits, explains or analyzes it, and applies requested edits by highlighting changed tiles for review before saving.
Event-based journey Start tiles can require a category selection that scopes who enters the journey and who direct message tiles can message.
From a Slack thread, Breeze can now update CRM records, enroll them in workflows, prep meetings and log calls.
Lets a published flow version move already-active users into it instead of only applying to new entrants.
Sign-up forms can now trigger and run as a native step inside automated flows, alongside email, SMS, push and WhatsApp actions.
Journeys can define a holdout group in journey properties to measure incremental lift via CJA; limited to select organizations.
Agents can create and edit journeys from a plain-language description, and help design, debug, and fix existing ones, but can't edit or run a live journey.
Prebuilt triggers and flow templates let retailers launch milestone, reengagement and replenishment journeys faster.
The journey canvas shows a content thumbnail for each channel activity, with a fullscreen modal to inspect and switch between treatments and variants.
Coworker Chat can produce a full-fidelity structured diff between two journey versions, including node and property changes.
Optional caching of Journey Live Data webhook responses for up to 10 minutes when requests are identical, cutting repeated endpoint calls.
A Coworker skill automates end-to-end journey validation (Quick Simulation flow) and helps interpret the results.
Recurring batch-audience journeys can wait up to 6 hours for a fresh batch evaluation before running, skipping the run if none arrives.
Journey Builder can deduplicate recipient email addresses within a journey to stop redundant sends.
A new alert flags when a live journey's entries, exits, or event sends deviate from baseline or drop to zero; production sandboxes only for now.
Journey Simulation now models Decisioning: content decision nodes, Optimize targeting, decisioned actions, and offer ranking policies.
Journeys/campaigns using Audience Composition audiences without a primary identity descriptor will stop working from the October release.
Journey creation with AI moves into the Coworker right rail, replacing the previous AI Assistant entry point.
Now GA (12 Oct 2026). Current summary: A Stop action activity in the journey canvas removes a profile from up to five inbound activities or experiences, decoupling inbound disqualification from journey exit.
Now GA (28 Sep 2026). Current summary: The journey canvas shows a content thumbnail for each channel activity, with a fullscreen modal to inspect and switch between treatments and variants.
Journey Properties' Set event recovery timeout setting replays impacted journey events for up to 72 hours after a service interruption by default, with a configurable 0-72 hour window.
Operator can draft a new Canvas or edit an existing one from a natural-language description of entry criteria, delays, and messages, for review before launch.
Iterable auto-generates a summary of each saved or published journey that Nova Agent and other agentic workflows can query.
Journeys can call an external webhook at a tile to pull real-time data for branching and message personalization, optionally saved to the profile.
A new, opt-in journey canvas UI improves performance on large journeys with automatic layout and guided authoring.
Journey Simulation can now mock enrichment attributes from CSV or Federated Audience Composition external audiences.
Journey time delay tiles gain a next-matching-time mode to release members at a specific time of day and weekday.
Reusable journey node sets can be built once, stored in a Fragment Inventory, and dropped into any journey; supports cross-sandbox packaging.
Journeys can be validated against simulated, temporary users; now generally available after an earlier limited release, with Journey Agent generating simulated data.
A new dashboard compares flow revenue, conversions and deliveries across channels and time periods.
On-Demand Journey Execution lets marketers trigger a journey immediately using the latest segment data, without waiting for a full segment rebuild.
Journeys can now designate a supplemental identifier for external CSV or Federated Audience Composition audiences.
Non-recurring Read Audience journeys now auto-transition to Stopped once the last profile exits, instead of waiting for the 91-day timeout.
The Optimize activity can now deterministically route customers to journey paths by segment or profile criteria, instead of only random assignment.
Batch audiences in Audience Qualification nodes and Exit Criteria will block publication starting September 2026; streaming audiences required.
A selection of workflow actions now run across all workflow types on associated objects or custom data sources, such as adding contacts to a segment from a deal workflow.
Lets Flows Assist refine an AI-generated flow across multiple turns in one session, versioning each regeneration; available to Flows Assist MVP clients on DC-03.
Now GA (9 Jun 2026). Current summary: Reusable journey node sets can be built once, stored in a Fragment Inventory, and dropped into any journey; supports cross-sandbox packaging.
Now GA (9 Jun 2026). Current summary: Journeys can be validated against simulated, temporary users; now generally available after an earlier limited release, with Journey Agent generating simulated data.
Real-Time journeys add a 'Never allow re-entry' option so a profile can only enter the journey once, even if it re-qualifies later.
Workflows can trigger on 1:1 email object events, such as email creation, for internal automation around email records.
New configuration recommendations help improve the performance of running journeys.
Bulk selection on the Journey Dashboard lets teams filter and organize journeys more efficiently.
A Canvas step that sends users from one Canvas into another, letting Canvases that share a promotion connect directly.
Canvas context variables can now set a removal event or an expiration for Content Cards.
A Message step setting controls whether a user failing delivery validation advances to the next step or exits the Canvas.
The Optimize activity now handles all conditional journey logic, replacing the removed, separate Condition activity.
Canvas context variables can now set an expiration for Banner and in-app Message steps or drive personalized delays in Action Path steps.
Temporary variables scoped to a single Canvas entry, redefined on each entry so simultaneous journey visits keep independent state.
A Dataset lookup activity retrieves AEP record dataset data at runtime, now open to all entitled customers in Limited Availability.
Legacy per-channel journey activities (Email, Push, SMS, In-app, Web, Code-based, Content Card) are deprecated in favor of the single Action activity; no end date or migration given, and existing journeys are unaffected.
The Update Profile action can now update up to five profile attributes in a single node instead of one per node.
Journeys can now deliver outbound messages in controlled waves over time, reaching GA after a Limited Availability release.
Automated SMS/RCS conversations can now branch customers down different paths based on keyword or question responses.
A Canvas step that creates or updates one or more context variables as a person moves through the journey.
The workflow editor keeps a revision history showing who changed what and when, with a one-click revert to any earlier version.
Aligns Flow performance stats to the configured App Timezone instead of GMT and extends real-time entry to Custom Segments, replacing a prior 3-hour refresh lag.
A generic Action activity now configures single or multi-action groups for any channel, with optimization, experimentation, and multilingual options.
A Content decision activity integrates personalized offers into journeys, usable in conditions, custom actions, and other activities.
AI agent that turns a text description of a journey into a fully structured, multi-stage Flow, auto-configuring triggers, delays, and conditional splits.
Now GA (16 Mar 2026). Current summary: Journeys can now deliver outbound messages in controlled waves over time, reaching GA after a Limited Availability release.
Direct Mail, previously campaigns-only, is now usable on the journey canvas for both batch and 1:1 scenarios.
Adds RCS as a native Flows channel for Android, with rich templates, personalization, A/B testing, event-based branching, and SMS fallback.
Custom actions can now define an error response payload, exposed in the journey's timeout/error branch for fallback logic.
Journeys can now combine Adobe Campaign v7/v8 message actions with native channel actions in the same journey.
Journeys now show warnings and errors when payload size approaches or exceeds recommended limits while building or publishing.
Profiles can now re-enter segment-triggered flows when they re-qualify, simplifying replenishment and re-engagement use cases.
Journeys support context variables that set values about a user for reference in later sync tiles as they move through the journey.
The Is Updated entry-criteria operator now compares before-and-after field values so contacts enter journeys more accurately on CRM data changes.