Rave alert expiration time issue

Comments

7 comments

  • Avatar
    Blake Freeman
    Hi Stephen,

    We'll need to test this to see if it's replicable. We'll let you know tomorrrow!
    0
    Comment actions Permalink
  • Avatar
    Blake Freeman
    Hi Stephen,

    We'll need to test this to see if it's replicable. We'll let you know tomorrrow!
    0
    Comment actions Permalink
  • Avatar
    Robb Price
    Hi there Stephen!

    I'm going to test this out to see if I can get similar results. Can you let me know what expiry time you are entering is at GetRave? I want to test with that same value.

    Thanks!
    0
    Comment actions Permalink
  • Avatar
    Stephen Burns
    I had one minute expiry on Rise and 10 on Rave. Sometimes it shows for 1 minute and others 10. I would think if Rave is sending an expiry, Rise should honor that over anything put into Rise.
    0
    Comment actions Permalink
  • Avatar
    Robb Price

    Hey there Stephen,

     

    I was trying this all day yesterday and this morning with no expiry in Rise, 10 minutes, 5 minutes, etc...It ALWAYS went with what I put into GetRave. Now here and there is may have been 5 - 10 seconds off starting or ending the Alerts Presentation, but never to the values you were seeing. It always stuck to the expiry value I had listed in GetRave.

    Are you still seeing the same issue?

    0
    Comment actions Permalink
  • Avatar
    Stephen Burns

    Yes, I am, and I do experience a few second delay, but that isn't the real issue. For example, I just sent a test alert to my test monitor at 10:55 with an expiration of 5 minutes. It disappeared at 10:57. I'm also having trouble with interrupting alerts. If I send out an alert with a 5 minute expiration, and then I send a second out with a 10 minute expiration, it obeys the previous alert's expiration and disappears early. It behaves very unpredictably, so it makes it difficult to rely on it in a true emergency.

    0
    Comment actions Permalink
  • Avatar
    Robb Price

    I agree Stephen. This is one of those situations where I wish I could recreate the same issue, but mine were running great.

    I wonder...do you think it could be the network the Display is in? Have you tried in a different network to see if that makes a difference? It's just a suggestion to try out, just to give you an idea if that may be a factor here.

    0
    Comment actions Permalink

Please sign in to leave a comment.