I believe the classic scheduler will not start the next job until the current job is done, even if the current job can't run. That's the reason I wrote the Greedy Scheduler. Honestly, I don't see a use case for classic.

No need to send the logs/files if Greedy works

You can definitely control the scheduler with a terrain picture and artifical horizon limits. See for instance this video for setting up the terrain image www.youtube.com/watch?v=fk2-Ow1tl1s and for instance see this post re setting up an artificial horizon indilib.org/forum/wish-list/6721-ekos-sc...onstraint.html#74088

Setup logging as below (1- go to the setup tab, 2- select log, 3- choose verbose, file, and select most of the Ekos modules.