It's been a few years since then, and I've since changed employers. In that particular deployment, my team had actually written our own controller in C# to replace the one provided by Blue Prism, which got around some of the limitations of the 5.x platform that were present at the time (this being one of them).
Your order of tasks within a schedule looks correct, and the scheduler shouldn't be aware of which account is being supplied to Login Agent on that level. In theory, as long as it's a pool, it should allow you to execute the same process/schedule twice. If it's still causing problems, you might try experimenting with an active queue against your pool.
------------------------------
Ami Barrett
Solution Architect
Karsun Solutions
Plano TX
------------------------------
