thank you, that's what I was looking for 🙂

The background is that the pipeline is started in a CI/CD job. The script is started and then the CI/CD goes to the next step. The next job depends on the pipeline and should be executed only after this is finished.

Hi @<1552101474769571840:profile|DepravedLion86> , do you have something that reproduces this behavior?

hey @<1523701070390366208:profile|CostlyOstrich36> this script doesn't actually work sorry

now this test.py reproduces the error actually

@<1552101474769571840:profile|DepravedLion86> You shouldn't need to call wait explicitly. What happens if you don't?

the script test.py terminates local. But I would like the script to terminate after the pipeline is finished.

or, if you want the steps to be ran by the agent, set run_pipeline_steps_locally=False

Hi, yes here:

Oh I see what you mean. start will enqueue the pipeline, in order for it to be ran remotely by an agent. I think that what you want to call is pipe.start_locally(run_pipeline_steps_locally=True) (and get rid of the wait ).