This issue has been resolved now as per internal sources :-). The functionality has been returned to previous state, regret any inconvinience