Hmm perhaps one way is to allow passing of a previous job parameter to the DeviceJob class. Then the function that launches a job chain should schedule all n jobs at once so that they are atomic. The nth job should check if the n-1th job finished successfully, if so, it should run, if not it should abort.
Sounds reasonable?
|