Changed from ; to &&

[Kortho]

&& continues the run if the previous command executed correctly, where ; does not and can cause problems

[ventz]

@Kortho This one can cause problems. The reason we actually changed from && to ; is because some commands while executing cleanly do not return 0 (or sometimes even return). Every once in a while this can bite you. Normally, completely agree that you want to reply on "X, Y, Z" happening consecutively, but there are too many moving parts here, and we have seen "non clean" (vs error) codes multiple times show up as randomly as they disappear.