This record is generated by AI from the cited source. How AI is used
Recurring batch-audience journeys can wait up to 6 hours for a fresh batch evaluation before running, skipping the run if none arrives.
- Platform
- Adobe Journey Optimizer
- Capability
- Journeys · Orchestration
- Vendor's name
- Trigger after batch audience evaluation
- First recorded
- Record last updated
Record dates describe acquisition and updates, not human review. About corrections.
Lifecycle history 1 state
- GA18 Sep 2026First recorded 27 Sep 2026 · recorded from the source history · vendor release notes · experienceleague.adobe.com ↗ · archived copy, 26 Sep 2026 ↗
Something wrong or out of date in this record? , ideally with a link to better evidence. How corrections work
Journeys on other platforms latest first
- KlaviyoVersion history for flowsGA9 Nov 2026
- IterableJourney Loop tileGA20 Oct 2026
- MoEngageFlow versioning: migrate active users to a new versionGAOct 2026
- MoEngageRestore a previous flow version as draftGAOct 2026
- HightouchCategory-based subset selection on journey Start tilesGAOct 2026
- IterableJourney Live Data response cachingGA24 Sep 2026
- SFMC EngagementJourney Builder email address deduplicationGAweek of 16 Sep 2026
- SFMC NextPrebuilt retail journey triggers and flow templatesGASep 2026
- HubSpotWorkflow enrollments preserved on record mergeGAAug 2026
- IterableJourney Live DataGA21 Jul 2026
More from Adobe AJO in Journeys
- Inbound activity deactivation journey activityGA12 Oct 2026
- On-demand journey validationGA9 Oct 2026
- Supplemental ID in journey simulationGA28 Sep 2026
- Jump activities in Audience Qualification journeysGA22 Sep 2026
- Path Experimentation support in Journey SimulationGA15 Sep 2026
- Reduced step events for wait and event activitiesAnnouncedSep 2026