Connection runs are now scheduled exactly every 3 minutes. In the rare case that a connection run takes longer than 3 minutes, missed runs are skipped, but the next run will match the original schedule.
Previously, there was a three-minute delay between one run finishing and the next one starting.
Events that start and end at the same date/time (i.e. which have a duration of 0 minutes) are now handled correctly by the time and duration conditions.
Previously, the time condition never matched such events. Worse, the duration condition would abort the connection run when encountering such an event.