Hi @<1546303293918023680:profile|MiniatureRobin9> could it be the pipeline logic is created via the clrarml-task CLI? If this is the case, I think this is an edge case we should fix. Basically it creates a Task instead of pipeline, which in.essence only effects the UI. To solve it, just run the pipeline locally, notice that by default when you start it, it will actually stop the local run and relaunch itself on an agent.
Also, could you open a GitHub issue so we add a flag for it?

Hi @<1523701205467926528:profile|AgitatedDove14> , yes the pipeline is created via the clearml-task CLI. I find it less constraining to launch a pipeline via the CLI. I'm opening a GitHub issue right now, hoping it will be fixed soon. Thank you for your answer 😁

Hi @<1546303293918023680:profile|MiniatureRobin9> , can you please add the full log of the run? Also, do you have some code that reproduces this?

Thank you! 🤩

Hi @<1523701070390366208:profile|CostlyOstrich36> , you can reproduce it with the pipeline of the iris dataset from the github None
I have a gitlab repo, I run this command to run this pipeline :
clearml-task --project test-iris --name pipeline-iris --repo ***.git --script pipeline/pipeline_from tasks.py --queue services --requirements requirements.txt --task-type controller --branch main
My agent is setup as a docker.
Here are the logs :