560 release feedback & discussion

Thanks @emerg.reanimator
We have similar issue reported internally with bug ID [4675920] and actively working upon it.