ASM signature in blocking mode after update (Not in staging)

Did it only affect updated signatures that were already in blocking mode, or did it affect new signatures that were added to ASM?

When updating signatures, there's an option that affects updated signatures:

Place updated signatures in staging:     Enabled 
Note: Newly added signatures are always placed in staging regardless of this setting.

If you see new signatures immediately placed into blocking, you should open a support case.

My ASM policy is in blocking mode (all signature in blocking mode). When I update the signature, I selected the option of keep the updated signature in staging mode, but the newly updated signature went to blocking mode.