You could make your own login process with a delay/wait stage at the end. It wouldn't mark it's self complete and move on to the actual job until it's actually done that way.
@PERSIC - That sounds perfectly reasonable. Moreso than the idea of trying to have multiple schedules. The problem with multiple schedules is threefold. 1) It's too easy for one of these events to be pre-empted by another job that is already running, perhaps due to having a larger workload than intended. 2) It's incompatible with a pooled resource model, unless you can tie in automated webservices or a custom-built replacement controller. 3) It's going to flood your visual schedule, which is prone to crashing Blue Prism (at least in 4x in 5x, I haven't tested in 6x).
Rather than have a series of scheduled tasks to login, process, lock/log out, you can also have the worker process call other processes, such as login/log out. This would allow for in-line exception handling, retries and reporting.