Incorrect routing after decision node

[jnovajosky]

We recently ran into an issue where tickets were being assigned to a specific team, then immediately assigned to a completely separate team.  We followed the workflow and were able to pinpoint a specific decision node that was causing the problem.

What was interesting is that the expression for this read as:

“Hornbill Automations->Get Request Info->Assigned Team == TeamName AND Hornbill Automations->Get Request Info->Owner is not set”.

So Hornbill should have picked up that the team was set to something else and the owner was set and followed the ‘No Match’ logic.  However, for some reason… it decided to assign to the specified team anyway.  I then updated the expression to read:

               “Hornbill Automations->Get Request Info->Assigned Team is not set”

Since the process I was following manually set a Team earlier in the workflow I again expected this decision node to follow the “No Match” logic.  It didn’t.

It was not until I got hyper specific and set the expression to say:

               “Hornbill Automations->Get Request Info->Assigned Team != TeamName OR Hornbill Automations->Get Request Info->Assigned Team != TeamName OR Hornbill Automations->Get Request Info->Assigned Team != TeamName AND Hornbill Automations->Get Request Info->Assigned Team != TeamName”

It was only at this point that the decision node correctly followed the ‘No Match’ logic pathway.

 

We are now seeing this across the organization and even in some of our Auto Tasks.

[jnovajosky]

This issues appears to affect any logical expression that checks the Assigned Team.

[jnovajosky]

@James Ainsworth

[James Ainsworth]

Hi @jnovajosky

A patch was released a few hours ago to resolve this issue.  I will check with you in the morning to make sure that all is working for you.