Changes to Pipeline Builder pipeline leading to breakage of unit tests

Hello!

When we are making a change to our Pipeline, such as removing an upstream input node, the node shows a Schema error.

We are not able to recover the broken node (cannot adjust input on the node and cannot drag the node), so the solution is currently to create a new unit test and manually copy the data from the original (broken) one.

Is there a more efficient way to recover the node in this scenario?

Thanks,
Tom

Hey, thanks for posting! Could you share more details as to whether the issue is that the pipeline is broken due to the schema error, or that the unit test is unable to be adjusted/dragged? This would be helpful to make sure I understand the exact issue here.

If the issue is with the unit test being broken specifically, would duplicating the unit test (in a unit test, the three dots next to the “Run Test” button) and updating the data to match the new schema work?

It is more related to the unit test being unadjustable/having to re-create it from scratch. I just mentioned the Schema error in case it was relevant.

Thank you for the suggestion, I will pass that onto the team and keep you posted if it is a suitable alternative!