How to Re-Enter a Journey Triggered by a Read Audience in AJO (Journey Entry Capping Testing)

[DiegoPa6]

Hi Adobe Community,

I’m currently running tests on the new Journey Entry Capping functionality in Adobe Journey Optimizer (AJO) and have a question related to journeys triggered by a Read Audience.

In my setup, a profile enters the journey and eventually exits through one of the designated end nodes. What I’m trying to achieve is for that same profile to re-enter the journey at a later time either after being removed from the audience or after some condition changes.

Here’s what I’ve tried so far:

• Once the profile exits the journey, I remove it from the audience.

• Later, I reinsert the same profile into the audience (e.g., via a query or attribute update).

• However, the profile does not re-enter the journey.

I’m wondering:

• Are there any known conditions or limitations that prevent re-entry into a journey triggered by a Read Audience? I’ve respected the “Allow re-entrance after” setting in the journey configuration  it’s currently set to 5 minutes, as is the default behavior.

• Is there a specific approach recommended for enabling re-entry (e.g., waiting period, using additional audience criteria, or manipulating timestamps)?

• Could this behavior be related to the new entry capping functionality, even when it’s disabled or not triggered?

I’d appreciate any guidance or documentation references you might have. I'm testing this as part of a broader effort to implement controlled re-entry logic for recurring journeys in a banking use case.

Thanks in advance!
Diego Parra

[SatheeskannaK]

@DiegoPa6 Did you wait for the next audience evaluation to complete after reinserting the profile to reenter into the journey?

[DiegoPa6 · Accepted solution]

Hi SatheeskannaK,

It was a misunderstanding on my part when I discussed this topic with the Adobe Support team. Based on their explanation, Journey Entry Capping is not currently working for unitary events, but it does work for Audience Qualification.

The confusion came from the mention of "Read Audience" I interpreted it as the Read Audience node, but in reality, those audience nodes are one-shot. So even if I remove a profile that already passed through a journey, it wouldn’t be able to re-enter the same journey, since it's not an event-based trigger but rather a one-time audience read.

Now that this is clear, I can move forward with my tests.

Regards,

Diego P.