Turns out it is a Bug.

Was it supposed to be fixed in Patch # 380?

'Cause it is still happening.

Thanks.