There may be iterations on a funnel like when a user is importing media they could have:

1 - : User begins the process of importing selected media

2a - : One of the selected media items is imported successfully

2b - : The next selected media is imported successfully

2c - : The next selected media is imported successfully

2d - : The next selected media is imported successfully

...

2z - : The next selected media is imported successfully

3 - : The entire media import process has concluded successfully returning the user to the editor

Indicating that a step can be iterated is useful for understanding collected sets in analytics. For us, events that share a single trigger also share an instance guid that allows us to connect that specific set of events for that specific instance the user triggered them. If we knew what an event could appear iteratively in a connected event set, we would also know not to worry if the same event shows up multiple times with the same instance guid, which should otherwise never happen as they should not be reused across different instances.