I found what I consider a bug in 8.2.4. I have a job where the task flow explicitly declares the next step to execute on success. I had that specified step (the next step) inactivated but it fired anyway.

My expectation was that since that specified step was inactive, the job would simply have stopped (no valid next step to go to). It appears that if a step is specifically indicated in the flow from a previous step, the active/inactive status of that step is ignored.