Chain Command Block Repeatedly Triggering

The repeating command block is activated, thus the whole chain runs their command; conditional command blocks do NOT end the chain if they fail their conditionality check.

In the future, please make sure you understand the mechanics properly before reporting behavior as a bug.

So even if the there is no output from the repeating command block as shown by the comparator and redstone lamp, and none of the other commands are running in the whole chain since the commands are all set to only executing if certain scores are set to specific values, they are all still running even though none of them are outputting anything?

Also the problem isn't within the commands themselves its the rotated Command Blocks that are acting up if the Command Chain was strait instead of curved it would work fine but can't do that for space issue in build so I curved it and before making this bug report I spent 4 hours trying to figure out what the problem was studying how Chain Command Blocks work watching multiple vidoes as well where in each video this was not a problem.

Running != succeeding; the repeating command block is running, but the command fails thus no comparator output.

Conditional command blocks check the command block behind them, not the previous one in the chain (if they did, conditional repeat/impulse would make no sense).

This works as expected; if their condition is not satisfied, conditional command blocks don't break the chain but only skip running their command and continue with the next command block. Similarily, an invalid command doesn't break the chain either.