What amibarret says is true for the latest updates of each minor version of BP 6.2 and 6.3 (and of course includes 6.4).
Sachin, what you describe is true for older version of Blue Prism, but along with the Scheduler updates that were made as patches to several BP versions, the option was added for a Post-Completion delay. So, before we had to create 2 schedules: one for login and one for the main process (and a second task for logout if you wanted it) because just as you describe, the resource would disconnect from the app server temporarily while it switched from being a Login Agent Runtime Resource to Blue Prism Runtime Resource.
But as of those updates (I think as of 6.2.2, 6.3.1, and one of the BP 5 versions) to Scheduler, you can use the Post-Completion delay. So, you only need one schedule with (for example) 3 tasks: (1) login with a post-completion delay of perhaps 120 seconds, (2) the main process, (3) logout.
Respectfully,
Dave
Dave Morris, 3Ci at Southern Company