I understand that and I really like this UX.
For now I'm using the published state to get the latest result available (artifact). I'm using it wrong I guess and should use tags or dates instead. But it helps me to have only one experiment tagged as published which would be the only ground truth (and if a new one comes it takes that role)
FrothyShrimp23 , I think this is more of a product design - The idea of a published task is one that cannot be easily changed afterwards. What is your use case for wanting to often unpublish tasks? Why publish them to begin with? And why manually?
Thanks CostlyOstrich36 , I guess there is no option in the UI for now ?
Thanks for the quick reply, really appreciated. Would you like me to open an issue or something similar if it's a feature you think could be helpful ?
Hi FrothyShrimp23 , you can use Task.mark_completed() and use force=True
https://clear.ml/docs/latest/docs/references/sdk/task#mark_completed