Command Timing Incorrect/Inconsistent

Windows_Minecraft - Release_516590

Summary: Watch the video on this one. The chain command block is supposed to shut off the command chain, but the chain will run 3 or 4 times once receiving a successful output into the chain block. The video shows 10 tests of this setup in Bedrock. The command returned 3 positives 3 times, and 4 positives 7 times. The video then shows the expected behavior (from Java), where the command is successfully shut off in one tick.

Impact: Commands cannot be run at the correct timing when utilizing this system. Using this to detect a success/failure will provide multiple successes/failures, which makes game logic difficult if not impossible to manage. Additionally, it isn't even consistently returning the same wrong number of successes, which means the game is taking different amounts of time to run the sequence.

Repro Steps:
1. Create a world
2. Set up command blocks as shown in the video. Make sure the repeating block needs redstone, and the chain is always active and conditional.
3. Repeating Block: execute @a ~ ~ ~ detect ~ ~-1 ~ snow 0 tell @s success
4. Chain Block: Make this block set the point of activation from a redstone block back to air.
5. Step onto a snow block, or set one beneath you.
6. Repeat this test multiple times.

Observed Results:
3 or 4 successes are returned.

Expected Results:
1 success should be returned every time.

Screenshots/Videos attached: https://youtu.be/A_FslciNlHE

There is potential this relates to MCM-129.