Well, I think I might be able to close this question - we restarted our servers this morning. And this issue was fixed by itself. It's magically working now. I tried the same scenario and this issue is no longer existing.
I may guess there were some issues happened when we our multi-nodes sync up on security rules or custom property. I will go back and check if I can find more proofs.