Minecraft Bedrock appears to process certain game logic across multiple threads. Because these threads do not always finish their tasks at the same time, the resulting update order becomes inconsistent and unreliable. This directly affects systems that depend on strict tick‑accurate behavior, such as complex Redstone mechanisms.
As server or client lag increases, the update order becomes even less predictable. This makes reliable Redstone behavior extremely difficult and, in many cases, practically impossible.
Impact on Gameplay:
Redstone circuits that depend on consistent timing fail unpredictably due to desynchronized updates between threads.
Falling block entities (e.g., sand, gravel) sometimes fail to update when landing on a block.
They remain as entities for a short period instead of converting to solid blocks immediately.
This can cause the falling block to break unintentionally, which disrupts designs that rely on stable falling‑block behavior.
When large numbers of falling blocks are present some of them will still be in the air for a short time after the other one landed (can be an intentional game performance design)
Please read the comment from the other moderator on MCPE-239094.