Affects Version/s: 22.214.171.124 Beta, 126.96.36.199 Beta, 1.14.60 Hotfix, 1.16.40 Hotfix, 1.16.201 Hotfix
Fix Version/s: 188.8.131.52 Beta
Platform:Windows 10 - PC
This can be tested by placing a chest, then placing something inside that chest.
Now place another empty chest above the first.
Use the clone command to clone the first chest over the second chest.
"No blocks cloned"
Open second chest and notice the items that were in the first chest are also in the second chest.
No doubt the reason it says failed is because the blocks are identical and the block itself was not actually replaced, even though the "contents" of the block were replaced.
However, I've seen this behavior in the wild when cloning different blocks over each other (hard to reproduce), which breaks the rest of the conditional command block chain. I've resorted to ensuring the clone update is the LAST operation in the chain because of this unreliability, or spitting out a redstone pulse to a repeater, then to redstone and finally to impulse+redstone command blocks. Ugh.
This does the same thing for signs, which makes it difficult to update signs for mini-games because the conditional command block chain halts at the clone operation, even though the sign is updated correctly with the cloned source contents.
IMHO the result should always be a success unless the clone operation is blocked by some other factor, such as placing blocks outside the valid world boundaries. (I'm sure others that have used this behavior on purpose would disagree with me.)