Whenever any value of a command block is updated, it just stops all responses completely and doesn't run the command. This is only fixed if you switch the status from "always on" to "powered" and then back to "always on" as observed in the video below:

Steps to reproduce:

1. Take any command block, possibly a repeating one for quicker demonstration purposes
2. Type any command in it, as long as it has a valid syntax and can run on repeat
3. Turn it on
4. Change literally any aspect of the command block
5. The command block stops working and doesn't run anything
6. Change the power status from "always on" to "powered," then back to "always on" in order to reset it.

Expected results:

1. Take any command block
2. Type a valid command in it
3. Turn it on
4. Change any aspect of the command block
5. The command should keep running even after the block is updated

This has never been an issue before. It is an extremely annoying bug since i basically need to turn off and on my command block every single time i update it or even change the command. I hope that this gets fixed soon because it is just unbearable and it could potentially break entire systems.