Journey steps is having more count of users than the previous/entry step.

Author: Panandhan22

src/engage/faqs.md

@@ -122,3 +122,7 @@ Yes, Engage supports the ability to send an audience or computed trait to two or
 An audience/computed trait Run or a Sync may fail on its first attempt, but Engage will retry up to 5 times before considering it a hard failure and display on that audience/compute trait's Overview page. As long as the runs/syncs within the specific Audience's Overview page say they are successful, then these can be safely ignored.  The Audit Trail logic, however, is configured in the way that it simply notifies about every task failure, even if it then later succeeds.
 
 If your team would like to avoid receiving the notifications for transient failures, please **[reach out to support](https://segment.com/help/contact/)**, who upon request can disable transient failure notifications.
+
+## Why the user count in a journey step is greater than the entry/previous step of the journey?
+
+Each step of a Journey is a Personas audience under the hood. The conditions 'stack' so a user has to be a member of the previous step (audience) and meet all the conditions of that current step to get added. Additionally, users cannot exit journeys once they have been added, but they can 'leave' a step (audience) if they no longer meet that step's conditions, even though they will still pass down to the next step. So, if the user no longer satisfies the entry condition will leave that step itself and user count will be reduced. And the user entered the next step will remains there until and unless the user fails for that step's condition and the count won't be reduced.