I'll share some screenshots

` # define pipeline
pipe = clearml.PipelineController(
name=TASK_NAME,
project=PROJECT_NAME,
version='0.0.1',
add_pipeline_tags=False,
)
pipe.set_default_execution_queue('default')

Adding steps

pipe.add_step(name=f'{start_date_train}_{end_date_train}_choose_best',
base_task_project=CHOOSE_PROJECT_NAME,
base_task_name=CHOOSE_TASK_NAME,
parameter_override=params_override,
execution_queue='default')
...
...

Execute the controlling task on a different queue

pipe.start(queue="pipelines") `

One sec I'll paste the relevant pieces of code

Sounds like some issue with queueing the experiment. Can you provide a log of the pipeline?

and the step is "queued" or is it "queued" in the pipeline state (i.e. the visualization did not update) ?

WackyRabbit7 I might be missing something here, but the pipeline itself should be launched on the "pipelines" queue, is the pipeline itself running? or is it the step itself that is stuck in ""queued" state?

it's double weird, because also a task that the pipeline says is "in progress" is actually completed

one sec

can't remember, I just restarted everything so I don't have this info now

the pipeline was running

but the task pending says its in the queue

queue looks empty

CostlyOstrich36

Do you need other part?

How did you call the steps in the pipeline?

CostlyOstrich36

ClearML results page: Launching step: 2019-09-03_2021-01-25_choose_best Parameters: {***********} Configurations: None Overrides: None Launching step: 2019-10-23_2021-01-15_choose_best Parameters: {************} Configurations: None Overrides: None Launching step: 2019-05-26_2020-12-26_choose_best Parameters: {**********} Configurations: None Overrides: None Launching step: 2019-07-15_2021-01-05_choose_best Parameters: {************} Configurations: None Overrides: None Launching step: 2019-02-15_2021-02-04_choose_best Parameters: {**********} Configurations: None Overrides: None