Whilst I was making a maze generator in bedrock, I decided to make some commands that would randomly decide where the exit would be. All the commands I used were the same kind that had worked before, but when I activated them, it just flat out refused to work past the second chain command block.

    Everything I could possibly do on the command block was in order, it was a chain command block, it was facing the right way, there was nothing wrong with how the command was written, it was set to 'Always Active' & 'Unconditional', there were no other command blocks that interfered with its command, there was absolutely nothing wrong on the surface. Even some repeating command blocks still set to 'Always Active' & everything else they needed (which I set up to check what number was on the scoreboard) refused that there was ever a number on the scoreboard! Once again, no other interfering command blocks, all the right settings & correctly spelled commands.

EDIT:

(I'll Put This In A Comment As well) So, I managed to get the command blocks to work. Turns out, the repeating command blocks were too near to spawn? this bug has occured to others, in which repeating command blocks don't update in spawn chunks, even when set to 'Always Active'.

    But The other problem with the chain command blocks appeared to be that I was activating two different command block chains with the same redstone block being placed in betwixt them... which still makes no sense at all to me. I don't know if this is a bug or intentional for whatever reason... but still, weird thing to need for working command blocks.