From the traceback ( backend_interface/task/task.py, line 178, in __init__ ), notice it's not Task.init

UnevenDolphin73 , how can you tell that ClearML is trying to initialize a task when get_task is called?

I'm not sure why internally ClearML tries to initialize a task when get_task is called...

~20

How many tasks do you figure this thing is iterating through the project?

I have selected the correct project indeed

Can you add a print out to verify that you selected the correct project?

It's a small snippet that ensures identically named projects are still unique'd with a running number.

proj_suffix = "" i = 2 while Task.get_project_id(f"{proj_name}{proj_suffix}") is not None: tasks = Task.get_tasks(project_name=f"{proj_name}{proj_suffix}") if not [task for task in tasks if not task.get_archived()]: # Empty project, we can use this one... break proj_suffix = f"_{i}" i += 1

I can see the task in the UI, it is not archived, and that's pretty much the snippet, but in full I do e.g.

UnevenDolphin73 , can you provide a small snippet of exactly what you were running? Are you certain you can see the task in the UI? Is it archived?