3 Replies Latest reply on Oct 17, 2017 8:41 AM by julieryan

    Inbox failure

    mikhaillenko

      Hi all,

       

      I would like to add another aspect of problematic Inbox behavior observed in Known & Fixed Issues in Jive-n and Jive-x Current Release (2016.3)

       

      That document identifies a bug about notifications marked as unread are not marked as read until the page is refreshed (merely clicking on the notification does not change it from unread to read). We are experiencing this behavior.

       

      In addition to the problem above, we're experiencing the following: Unread Inbox notifications are not prompting the Inbox icon to show that there are unread notifications, along with the number of corresponding unread email notifications. (The Inbox icon suggestions I have no unread messages; the unread messages demonstrate there are  indeed unread messages.)

       

       

      https://castlighthealth.jiveon.com/groups/castlight-employee-profiles/blog/2017/10/13/insert-title-of-social-club-event-here

      Kindly,

      Mikhail

        • Re: Inbox failure
          julieryan

          Hi mikhaillenko - we seem to be experience the same issue (it started about 2 weeks ago for us...). Please share any information you may come across regarding this.... We'll do the same.

          1 person found this helpful
          • Re: Inbox failure
            gvdd

            This behavior will be probably related to CLOUD-6322

             

            As a quick fix support manipulated below 'system properties'

            1) Step 1 is to set / edit them from their default state to the following:

            stream.polling.enabled = false
            stream.websocket.enabled = true

            2) Step 2 is to set them back to what they are supposed to be (default state)

            stream.polling.enabled = true
            stream.websocket.enabled
            = false


            As on cloud you don't have access to these 'system properties', you should start a private support case to get this resolved

            3 people found this helpful