When merging data, there is a tree-like HTTP request in one of the pipelines. How to ensure correct consolidation results

Although I have other solutions to this problem, such as removing the “if” node and allowing all texts to be translated twice, I want to know how to deal with it correctly if there are multiple conditions and multiple requests.

Hey @duttchasel, if the order of your items can change on one of the two input branches of your Merge node, I’d suggest avoiding the Merge By Index mode and use the Merge By Key mode instead.

Now your items might not have a suitable key value yet allowing you to merge them, but you could add one for example as described here: How do you guys deal with this situation? - #3 by MutedJam