This may be possible but I have yet to figure it out.
Assuming you have a sequence with two (or multiple events) . The first event is scheduled for 3 hours of imaging, but the unfortunately misplaced tree interferes with the imaging run. The sequence goes into recovery mode and eventually aborts.
The recovery mode should be configured to go to event 2 rather than totally aborting the sequence (after X attempts or if time of start of the second event > current time or it is still night out)