How do I avoid the advanced branching error "The provided smart value was unable to be resolved"?

[Patrick Haley]

Hey everyone, we use an external Jira account with one of our vendors so I created an automation to link issues together whenever an issue key from the external project is mentioned in the comments. The automation works as intended when a comment contains the issue key, but it results in an advanced branching error when a matching issue key is not found in the comment saying "The provided smart value was unable to be resolved to an object." I'm wondering if I'm just missing a step in the automation logic to stop this error. 

Here's an example of the audit log where you can see it works when the comment contains GJGSAM but results in an error when it does not.

[David Pezet]

It seems like maybe the erroring issue does not have a match so the Smart Value is resolving to null. You might try adding an IF condition at the start to make sure there is a match before executing the branch.