Aha, it looks like the pipeline steps remember what the current git revision was when they last ran, so the cloned steps get that rev. That kind of makes sense, but it's also annoying.

Is there any way to tell pipeline steps to get the latest HEAD revision from the repo when they run?

Thanks, I'll try that. But it seems to be doing what I expect, now. If I make changes to a step (task), I have to run it once to register that version of the task in the ClearML DB, and the pipeline pulls the rev that was current when that step was registered.

Hi @<1760474471606521856:profile|UptightMoth89> , what if you just run the pipeline without run locally and then enqueue it (assuming you have no uncommitted changes)