613c850 created the issue

Using nightly build 8225, Mac OS X.

I set my maximum transfer limit to one, then queued several transfers. When the first transfer completed, Cyberduck started the second of the pending transfers, rather than the first. When that transfer completed, the third of the remaining transfers was started. Next was the second in the queue. It seems Cyberduck is picking a random queued download to start when there are available transfer slots, rather than picking in the order in which the transfers were queued.