Delayed "SuccessCount:1" CommandBlock Update.

Idk, I just made a bug report on my own (MC-87611), no idea whether you meant the same thing or something else which I don't understand from your description..

It's a similar issue Frank. The only difference being you are using an impulse commandblock while I am using a repeating one.

My bug report on the other hand shows what seems to be causing this issue, being the SuccessCount not updating at the right time. By the looks of your report, it seems to be updating one block at a time through each pulse.

Since the SuccessCount is still 1, the conditional commandblock next to it will still work because the SuccessCount is what say whether the condition commandblock should run or not.

So by the looks of your report, the SuccessCount NBT of the commandblock before each of your conditional commandblocks looks like the following:

Test 1
[@] 1 SuccessCount:1
[@] 2 SuccessCount:1
[@] 3 SuccessCount:1
[@] 4 SuccessCount:1

Test 2
[@] 1 SuccessCount:0
[@] 2 SuccessCount:1
[@] 3 SuccessCount:1
[@] 4 SuccessCount:1

Test 3
[@] 1 SuccessCount:0
[@] 2 SuccessCount:0
[@] 3 SuccessCount:1
[@] 4 SuccessCount:1

Test 4
[@] 1 SuccessCount:0
[@] 2 SuccessCount:0
[@] 3 SuccessCount:0
[@] 4 SuccessCount:1

So, MC-87611 was just flagged fixed. We'll find out if that fixed this issue, too, when the next Snapshot gets released.