Command block running issues due to archive location change

I have encountered this problem multiple times in the past two months. When opening a save in a specific situation (usually with over 1000 running command blocks), all command blocks of the save will not run, regardless of their type, even if they receive a redstone signal, remain open, or the game settings enable command blocks.

The above situation is referred to as the abnormal running state of the command block. I have listed several specific triggering situations below and noted the duration of the abnormal state. When the version is upgraded, the command block of this archive will encounter an abnormal state: the first time is from version 1.20.51 to version 1.21.62.01, and the second time is from version 1.21.62.01 to version 1.21.82.02; When the archive file is moved: When I try to compress the archive folder into a compressed file in the phone file manager and re extract it to the game map folder, this archive will have this abnormal state from then on; 3- Duration of abnormal state: A map archive that has already experienced an abnormal state, I have tried many methods but have not been able to solve it, and as the number of version upgrades and archive file migrations increases, the duration of the abnormal state has changed from waiting for tens of seconds to automatically resolve after entering the game to now being completely impossible to resolve automatically.

Finally, I attempted to replace the level.dat file, which actually exacerbated the issue. These command blocks that are in an abnormal state can be manually opened, set to require Redstone activation, and then opened again, set to keep running. Single command blocks can be released from the abnormal state through this method. But when the player exits the game and re enters the map, all command blocks will re-enter this abnormal state. For an archive with over 1000 command blocks, this is fatal. If necessary, I can provide a compressed archive file that I currently hold and has encountered this issue. The current version is stuck at 1.21.82.02.