Trigger unexpectedly firing

3 Comentarios

  • Chandra Robrock
    Community Moderator
    Most Helpful - 2021

    Interesting! I have a similar trigger that looks for specific keywords to mark the ticket's Priority as Urgent and the Ticket is Created condition is enough so that agents can manually update the Priority back to Normal if a ticket has one of those keywords but isn't actually urgent.

    Have you checked the Ticket Events to ensure that it's the same trigger that is flipping the ticket's priority back to High? I wonder if perhaps there is a different problematic trigger at play here because your trigger looks fine on my end. 

    0
  • Boosey & Hawkes Music Publishers Limited

    Hi Chandra - thanks for your comment.  I just happened to watch your stuck ticket/SLA video on YouTube - funny coincidence!  

    The explanation turned out to be quite simply actually - isn't that always the way.  It turns out you can't set Priority to "-" if it's previously been set to 'High', but you can set it to 'Normal', so that's what we're now doing and it's working fine.  Phew.

    0
  • Chandra Robrock
    Community Moderator
    Most Helpful - 2021

    Ah, that's great! Such a funny coincidence indeed.

    I'm also glad to hear you were able to identify the issue! I was definitely stumped on that one because your trigger is even more strict than the one I use with since you have a nullifying tag as well. 🤣 

    Have a great rest of your weekend!

    0

Iniciar sesión para dejar un comentario.

Tecnología de Zendesk