(13269642) In scenario containing a synchronized fork with parallel branches referencing the same user segment, the wait for timer event gets reset when one branch succeeds.
In a scenario that has a synchronized fork with at least two parallel branches where each branch contains the same user segment and each branch contains a “wait for x time” element, the branches of the scenario run sequentially. Expected behavior would be for the branches to run in parallel. Consider the following example:

When this scenario is run, the first e-mail is sent two minutes after the scenario starts (which is expected behavior), but the second e-mail is not sent until seven minutes after the scenario starts (which is five minutes after the first branch completes). Expected behavior is for the second email to be sent three minutes after the first (five minutes after the scenario starts running).

Workaround: If possible, configure the timers to compensate for this behavior.