There is a configuration within the product (look in the product help for info) which is 'If a resrouce is offline, retry after:"" and 'Retry an offline resource a maximum of"".
These default to retrying after 5 seconds and trytring a maximum of 10 times.
However, this feature was created for offline resources (where there might have been a network blip) rather than busy resources. Maybe experiment with it to see if it would work for busy resources also?
I think the better solution would be either:
** Have your sessions as follow on tasks within the same Schedule rather than two seperate Schedules. Task two will start when task one ends - which is far cleaner.
** Or you could have an end time in process one that ensures it does not pick up new work after 10:55. That is no use if all items need to be worked.