Ticket Search condition does not match custom variable value

[Mark]

Hello all,

I have here a “Query for one object” step, querying for a Ticket…

I have confirmed there is no space behind the variable name, and that a ticket exists with this value in Title.

The step fails to return a match and the log seems to suggest it is due to a space char at the end of the CONTAINS query value…

Modifying the ticket to add a space in this position of the title and re-processing the message results in a positive match, seemingly confirming the issue.

I’m not able to spot what I’m doing wrong here.

Log is here if you see this Travis
https://console.mspintegrations.com/#/email2at/advanced/history/173706097602344

Mark

[travis]

Hi @Mark

Intriguing!

I can see that the configuration for that rule in the database does include the space, even though the space is not displayed in the UI when viewing the query step. (Side note: the UI always calculates the query, and doesn’t display the query that it retrieves from the database).

Please open the rule and save it (you don’t need to make any changes), and then replay the email. I suspect it might work, but please let me know.