Yes, a boolean flag for (3) would be a good option!
In (1), the code snippet from my original question is the code that I execute on my local machine. It is submitted to a queue with an agent that runs with docker. Please, let me know if this is enough to reproduce it.

Thank you for your reply AgitatedDove14 !
For the point 1, here is what is printed out when the task starts execution for the first timeSyncing scheduler Failed deserializing configuration: the JSON object must be str, bytes or bytearray, not NoneTypeHowever, now I see that this actually doesn't break the code, and this exception is ignored. The task is not started in the first run, but this is because of the reasons discussed in the point 3, I assume. Sorry for a false alarm here.
For t...

in this case this is just an example, it could be any module, e.g. for dataloading etc, which is part of a project. For utils as package, we will discuss this in the team, thanks for a suggestion!

Hello 🙂 I am also trying the pipeline out, and would love to chat!

Something like this
clearml-task --project YOUR_PROJECT --name SCRIPT_NAME --script PATH/TO/YOUR/SCRIPT --repo YOUR_REPO

WackyRabbit7
as TrickySheep9 mentioned, you can use clearml-task . It will create a draft of a task if you do not provide a --queue for it

Thank you for your reply AgitatedDove14 ; I found the option in clearml.conf ; we will use it for now 🙂 .
But a warning instead of an error would be good. Maybe a bit of a context for our use case: we use clearml-task to create components of a pipeline, we only create tasks and do not schedule them for the execution (so that the pipeline does it instead), so we do not expect the paths for the data storage to be available then. Does this sound like a reasonable workflow, or is there a...