Hi all, slightly specific question but does anyone know why the next step is required here? https://github.com/dagster-io/dagster/blob/8d5c99f038532f2264818556159b92ef45461c2[…]on_modules/dagster/dagster/_core/execution/plan/execute_plan.py This already seems to be within the child process, so not completely sure why the next step is needed?

You’re pretty deep in the internals here-- I’m somewhat familiar with this code but can’t recall immediately why that is needed. What are you trying to do? Or are you just studying the source?

Hi Sean, I'm trying to implement OP concurrency control across jobs. Figured a good place to start changing would be https://github.com/dagster-io/dagster/blob/7ab0151639cf658d563977f9263f85be748fb2e[…]2/python_modules/dagster/dagster/_core/execution/plan/active.py. Then I realised the function above gets called twice because the

get_next_step

function https://github.com/dagster-io/dagster/blob/7ab0151639cf658d563977f9263f85be748fb2e[…]2/python_modules/dagster/dagster/_core/execution/plan/active.py gets called from inside the child subprocess.