@janusofdoors glad you have worked out what the connection issue was.
The reason we have the event is so that different machines can have different responses to loosing can connection, and also different responses depends on the specific expansion board that has lost connection. There is unlikely to be a default that everyone is happy with, and changing the default does mean that anyone upgrading has to notice that the default has changed and take action to create event files. I do think having the config tool generate an example event file that acted differently if a job was running or not and.paused during a job could be a good compromise.
