At the moment it is considered a "success" when you stop a Job. What you can do is to use Job/Task control Tasks instead of Triggers in the end of each Job.
This has been a somewhat troublesome issue for the processes I work with too. VisualCron has enabled us to efficiently combine a whole host of different processes efficiently, integrating the unique dependencies that each have on one-another. Having such an integration with a variety of third party software, along with internal processes means that there are often minor issues that need addressing. In such cases, the processes running may need to be stopped, and then rerun once the fix is in place (typically within a few minutes). These fixes tend to be relatively unique and require manual intervention, so they are not something we can handle with additional job/task control at this point in time.
The only work-around that we have found is to disable any jobs that follow, then stop the job, re-enable the respective jobs and resume. The issue with this approach is that disabling the job resets all of the triggers, some of which cannot be triggered manually. It is also quite error-prone with the potential to disrupt the flow of the processes.
A suitable solution for this may be to allow the option to define what stopping a job is classified as (success/fail/stopped), or alternatively adding an additional option to the job triggers such as "Job completed - stopped", and similarly the job flow to determine "On stopped -> Continue/Stop".