An AJO daily entry cap does not protect a 14-day wait

A profile qualifies for two read-audience journeys on the same day. The team wants the higher-priority journey to win, then keep the profile out of other journeys during a 14-day wait. A community question shows why a one-entry-per-day rule looks attractive: it feels like a pause. Adobe's journey capping guide defines it more narrowly. Entry capping limits entries in a time period; concurrency capping limits simultaneous enrollment.

Write the policy before choosing the cap

Specify whether the rule means “one new journey today,” “one active journey at a time,” or “no re-entry into this journey while the person is still in it.” Those are different policies. Record the rule set, priority scores, UTC reset boundary, journey schedules, and whether the same rule is applied to every competing journey. Give priorities distinct values so arbitration is unambiguous.

Simulate the profile's timeline

Use a synthetic profile that qualifies for both audiences. Test the first entry, a second qualification during the 14-day wait, and a qualification after the first journey ends. Inspect Journey Exclusions for CAP_REACHED and LOWER_PRIORITY, and compare with actual journey entries. Adobe notes that look-ahead can suppress a lower-priority scheduled journey. The community discussion does not establish every outcome when a profile is already active in the higher-priority journey, so do not promise an undocumented fallback to the next one.

Keep the design within the clock

Adobe's global journey timeout is 91 days. A 14-day wait followed by a 90-day wait cannot fit in one journey. If the business wants a longer exclusion, model that state outside the journey and test when it clears. Ask for a timeline that includes UTC boundaries, overlapping audiences, and a report proving why each test profile did or did not enter.

Adovo’s view

Priority is not a customer policy until it survives time. The useful design is a readable rule for who may enter, while whom, and for how long. Make that rule explicit; then let the journey configuration prove it.