Pipeline set variable not saving expression values

looks like just a UI glitch in the pipeline editor, especially when you have multiple Set Variable activities referencing each others values in the same loop. The wrong expression often shows up in the editor pane even though logically the pipeline is still correct underneath (or it’s overwriting behind the scenes). In most cases, the final approach is simply to have 2 separate Set Variable activities in the Until loop: the 1st copies the old value to a temp variable, and the 2nd increments the original variable by referencing the temp. This is usually the cleanest workaround for the UI mixup issues.