murugesamgr

clear server site caching resolves this issue. am using nginx and server caching enabled. the bug gone out after disabling nginx cache