Sometimes when running jobs sequentially Job B may not require data, like a cache, from Job A, but still needs to be run after Job A's tests. It would help reduce workflow duration if Job A could have a step that triggers Job B to start while Job A finishes any "cleanup" steps, like saving a cache. Alternatively Job B could depend on a step's completion in Job A to start.