Profile cap condition not working in journeys - AJO

[LuisCardenas]

Hi all,

I'm using a profile cap condition inside a Journey to limit a certain number of profiles to be targeted by a subsequent email action. I've seen that it is not always consistent, and on ocasions it fails to reach the profile limit set.

ie: Journey triggered by an event (approx 1M profiles entered), profile cap condition of 760k profiles. However, only 614k advanced to next action, and the rest were discarded.

Any advice on why this happens? how to avoid it? any recommendations?

Attached is a screenshot for reference.

@Mayank_Gandhi @SatheeskannaK 

[SatheeskannaK]

@LuisCardenas Can you validate the following?

"For live journeys with a cap exceeding 10,000, the number of distinct profiles injected must be at least 1.3 times the cap."

- We need to validate that for 1 million profiles entered into the journey, approximately 988,000 distinct profiles were recorded.