@Nagios_Jzurge ok.
- Move to schedule.
running test for 24 is not good idea due to possible instability of long runs it is better and easier to run it on schedule. it helps to avoid writing workarounds to continue test from zero while catching absolutely all errors. i suggest switch to schedule with any available CI framework e.g. jenkins. You can even install it on same machine and run jobs on schedule. - Start driver with fastReset.
Different capabilities for different scenarios to reset app client before test and start from login each time.