Do not assume a B2B person journey inherits AJO's 91-day timeout

A long B2B nurture can span quarters. Before designing one, a team needs to know when an individual stops progressing. An Experience League question asked whether the 91-day limit documented for standard Journey Optimizer journeys also applies to B2B person journeys. The community reply did not confirm a matching B2B person timeout. That is a reason to verify, not a license to assume unlimited duration.

Separate two different clocks

Adobe's Journey Optimizer guardrails document a 91-day global timeout for an individual's progress in a journey. A configured journey end date is a separate lifecycle setting. Neither number should be transplanted to another product surface without product-specific documentation or written confirmation from Adobe.

Model the real nurture before choosing a canvas

List the longest expected wait, reentry rule, exit condition and what happens when an account changes stage. A person who misses a renewal or handoff because a journey silently ended is a customer problem, not merely a platform detail. For a journey that must last months or years, ask Adobe to confirm behavior for the organization's exact B2B product and version. Record that answer alongside the design.

Build a recovery path

Even after confirmation, define a durable business state outside the transient journey instance: stage, owner, next action and last completed step. Test an aged profile and a restarted journey, then decide whether the next action is resumed, recreated or handed to a human. Monitor exits and overdue steps so a timeout or configuration change becomes visible.

Adovo’s view

The customer relationship outlives any one orchestration run. Design around that fact. A journey can coordinate the next move; it should not be the only record of what the buyer is owed.