Regarding the 91 day journey end criteria | Community
Skip to main content
Stiwari
Stiwari
Level 1
February 26, 2026
Question

Regarding the 91 day journey end criteria

  • February 26, 2026
  • 1 reply
  • 18 views

Hi, 

I have a question regarding the 91-day criteria for journeys. We have batch evaluated journeys with read audience that are intended to be always on (evergreen) in the sense that we hope that profiles keep entering as long as the journey is live.

My question is once the journey is published what would happen after 91 days. We have not set any end date for the journey. 

Will it automatically move to finished state or will it continue to be live after 91 days. Also, in some documentation it says that after 91 days reporting data is not available or it gets refreshed. Is that case?

Any help would be greatly appreciated. Thanks!

1 reply

SatheeskannaK
Community Advisor
SatheeskannaKCommunity Advisor
Community Advisor
February 26, 2026

​@Stiwari 

Journey Ongoing Status

  • Audience evaluation is proceeding as planned.
  • New profiles are continuously being added.
  • Message delivery remains active.
  • The journey is currently Live.

Limitations and Data Visibility

  • Change Over Time: The reporting window only displays performance data for approximately the last 91 days.
  • Older performance data is not accessible within the user interface (UI).
  • Reporting data is tied with the dataset TTL. Have a look at this documentation,

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/create-journey/journey-properties#global_timeout

Look at this callout on the one-shot read audience vs recurring read audience journey. 

“

NOTE

One-shot Read audience journeys move to the Finished status 91 days (journey global timeout) after the journey execution. For scheduled Read audiences, it is 91 days after the execution of the last occurrence.”

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/about-journey-building/read-audience#schedule

Thanks, Sathees
    Terms & ConditionsAccessibility statement

    Loading footer...