Read Audience Journey not working as expected

Hi everyone,

I'm investigating a behavior with Read Audience activities in Adobe Journey Optimizer and would like to know if anyone has experienced something similar.

Scenario

• A profile meets the audience qualification conditions.

• The profile qualifies for the audience (confirmed in both Monitoring and Profile Snapshot Export).

• Batch audience evaluation runs daily at 18:00 UTC.

• The journey is configured with:

  • Read Audience as the entry activity.

  • Scheduled daily.

  • Trigger after batch audience evaluation.

  • 5-hour time window.

Issue #1

Journey A is scheduled to start at 21:00 UTC.

Although the audience contains qualified profiles after the batch evaluation, no profiles enter the journey.

Issue #2

Journey B is scheduled to start at 21:30 UTC.

A specific profile did not enter the journey on the day it qualified for the audience.

Instead, it entered the journey 24 hours later, during the next scheduled execution.

The strange part is that, at the time the profile entered the journey, it no longer matched the audience conditions, and the segmentMembership information in the Profile Snapshot Export showed the profile with status = exited for that audience.

Has anyone seen similar behavior with Read Audience activities?

I'm particularly interested in understanding:

• How the Read Audience activity determines which audience snapshot to consume.

• Whether there are known timing or synchronization delays between Audience Service and Journey Orchestration.

• Whether a profile can be picked up from a previous audience evaluation even if its current membership status is already exited.

Any insights or Adobe documentation explaining this behavior would be greatly appreciated.

Thanks!

​@SatheeskannaK