When monitoring policy opened by an user and his/her session gets timed out that policy goes into lock state. Resulting other users will not be able to eddit the policy untill that user or a super admin unlocks it.
If user re-logins and gets an auto-save copy of that policy and he/she can continue editing same policy, then it seems valid to lock that policy. But it is not like that in this case.
Case raised for same with BMC Support 00599912, Please consider this ask as this becomes an overhead on configurators and Admins to get it un-locked.