Thanks for your help Penar, we were able to fix the issue by using discourse-solved plugin from Feb. 19 (commit: 3b7baa1a513e5267d8213ceda09dd461f94cf9ad) with Discourse 2.2.0.
If we rebuild discourse with latest commit of the discourse-solved plugin, which version of Discourse do we need to take to avoid this issue? version 2.3.0? We don’t want to upgrade discourse to latest if this issue is not fixed.
Thanks.