| Tab | Description | Notes |
| Due | People who are due for a manually executed action. This will include people that are due today or already past due for this step. | Automatically sent steps will not show in the Due tab. |
| Not Yet Due | People who are active in that step, but not yet due or past due. They are essentially waiting for the corresponding actions for this day to become due. | Example: Someone who has just executed a day 1 step, but waiting for day 3. This person shows up as not yet due for Day 3 and Completed for Day 1. |
| Outbox | This is unique to email steps only, and refers to people that are pending an email being sent. This can happen when bulk send, schedule send, or automated send is used. | Throttle limits or send limits can also effect how many emails can be sent in one day. Any email sent after a users send limit has been reached will also show up in the outbox. |
| Paused | People who have been paused in the selected steps. | If you pause someone while they're active in a Flow, then they will show under the "paused tab" for their last active step. For example: If you pause someone on day 2, they will show up on the day 2 tab not day. |
| Failed | People who have failed from completing this step. This is usually due to the email being unable to be sent or us being unable to log the activity back to salesforce. |
List of possible failed reasons:
- contact_not_found
- opted_out
- merge_field_issue
- email_bounced (pre-send)
- user_cancelled
- invalid_sfdc_token
- invalid_google_token
- google_api_error
- invalid_recipient
- deactivated_user
- unknown
- flow_actions_limit_reached
|
| Bounced | A person who has bounced from an email step in a flow. If you do not have email steps, you would not expect to see people in this tab. |
- If a person is marked as "bounced" and has an activity in this step, it means they executed an action and should be marked as bounced.
- If the person was removed due to the bounce, then they will show up under the exited tab.
|
| Exited | People who have completed the Flow step but were removed from the Flow prior to completing the subsequent Flow step. This can happen as the result of an automated action, a setting, or the participant being manually removed by the user managing them in the Flow. |
Possible exit reasons:
- automated_action
- auto_remove_after_bounce*
- auto_remove_after_reply*
- flow_is_archived
- inactive_user
- logged_call_and_added_to_new_flow
- logged_call_and_removed
- manual_user_removal
*The auto_remove_after_bounce and auto_remove_after_reply settings were deprecated in October 2024 in favor of automated actions. New Flow participants will not show with these exit reasons. However, participants removed from Flows for these reasons prior to October 2024 will still show.
|
| Skipped | People that have been skipped in that step. | If a person is skipped multiple times, then this number can read higher than the number of active people in the flow. |
| Completed |
The total number of times the step has been completed within the flow.
Step totals can differ from the number of people listed due to repeated steps or if people are participating in multi-step days.
|
Single step: A person will be counted on a single step if they have completed this step and moved to the next one.
All Steps: A person is counted as complete if they have completed the last step in a flow. If they exited on a previous step, then they will be considered "exited" instead.
If a person is completed and then new steps are added to the flow, then that person will only be counted as completed for the steps that existed before.
|
| Opens | Open rate of emails sent in this step only if open tracking was enabled at the time that the steps were completed. If open tracking was not enabled or allowed, then this should be zero. | |
| Clicks | Click rate of links that are sent in this step as long as link tracking was enabled at the time of the send. If link tracking is not enabled, this should be zero. | |
| Replies | Reply rate of emails sent in this step. | |
