Automation - Validation failed for Insight object custom field

[kara.decker@jackson.com]

I am trying to setup an automation that uses a custom field to pull from an asset schema. This works for most of the assets but we get the error shown in the picture for some of them. There appears to be no rhyme or reason to the failure and all assets were imported from the same spreadsheet. Then the asset name copied and pasted into the AQL query. 

All other queries work and the one custom field that is giving an error works 75% of the time. 

Any insight on what might be causing the random issue? 

[Bill Sheboy]

Hi kara.decker@jackson.com 

For a question like this, context is important for the community to help.  Please post the following:

• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution with all the areas expanded

Until we see those...

Does your rule use JQL with the Schedule trigger, perhaps as a source of data for creating the new issue?

Next regarding asset data, I believe some of that is looked up just-in-time for use in automation rules.  As you observed this to be an intermittent symptom, I wonder if there is a timing problem where the data is not always present in time.  Some such symptoms can be mitigated by looking up the object data first and storing it in a created variable for use later.  Seeing the details of your rule's Create Issue action may help to confirm this.

Kind regards,
Bill

[kara.decker@jackson.com]

Hi @Bill Sheboy

Below are pictures of the rule in order from schedule, to create, then branching. 

My original post had the audit log details with all areas expanded. 

I do not use JQL. 

The field circled red in the 2nd pictures is the custom field referenced in the error message.  

We are using JSM for our Facilities team so I have limited IT knowledge. :)

How do I store data in a created variable for use later? 

How would this work if the automation was to run every week, month, quarter? 

[Bill Sheboy]

Thank you for that information.

It appears the create is failing with the AQL for the "Room Code" lookup.

On that field edit, if you select "Validate syntax", what do you observe?  Is there a result count shown for matches?

[kara.decker@jackson.com]

So I have never been able to have validate syntax return a result. It always gives an error. See picture. 

I can confirm if I remove the Room custom field that the automation runs correctly and the AQLs run correctly for the other fields

I can also confirm that we have no other assets that are "5301.1W.AQ09" so this is the only result to pull. 

I can also put other room codes in this field and the automation will run just fine the first time but it will fail on the 2nd run. At the same time we have others that will run without issue every time. 

Also I appreciate all of your help. 

[Bill Sheboy]

I believe that error is a rule scoping symptom. 

Is your rule single-project scope (in the details at the top)?  If so, to validate that AQL the rule must use a global scope...which a Site Admin will need to change.

[kara.decker@jackson.com]

Is this what you are talking about? 

[Bill Sheboy]

For your specific rule in the rule editor, look at the Rule Details at the top-right.  On that view you will see the scope setting.

[kara.decker@jackson.com]

Is this what you are talking about where the scope is specific to our project? 

[Bill Sheboy]

Yes, that is the one.

[kara.decker@jackson.com]

Thank you. I will ask them to change the scope to global. 

This should fix our validate syntax issue.

Do you also think it will fix the error that we are having? 

[Bill Sheboy]

I am not using Assets currently and so cannot test that, although I suspect if the AQL succeeds the rule will also.