Refresh cache and sanity issues with Delete member/Remove member API
Its observed while working on !677 (merged) that cache refresh and transaction rollback strategies are insufficient in Delete Member API.
Need to analyze and implement transaction rollback and cache refresh properly, so we don't end up doing it too many times and also in not required scenarios.