Attribute Rules Performance Issues

[Smileyk_mdt]

Hello,

I'm drafting and testing some attribute rules from a copy of a GDB someone sent me. I have some validation rules that work well, but only if I export the feature classes to my own file GDB. If I run the same rules on the one they sent me, they get stuck and run infinitely. No telling how long but i stop it after an hour.

For context, the gdb they sent has everything in our LRS in it. It has the LRS dataset as well with the ALRS controller. I'm not at liberty to share it, and I'm not sure what version it was created in. it does have all the validation tables in it. Global IDs are enabled, editor tracking enabled, and all features are checked to participate in visual review.

Has anyone had this issue? My arcade code works fine when I export feature classes from it and test on another map. Perhaps its normal and takes a day or two to run on the gdb with everything in it? 

[JayCary]

There are two supported implementation methods (Arcade and ArcGIS Data Reviewer) for validation attribute rules. You may want to review your server log to see which rule(s) are taking the most time to complete.

Here is a link to a technical workshop that discusses using server log to identify rule performance.

[James_Blouin]

Hi. The long runtime might be normal depending upon how many validations you have and what your map extent is before running your validations. LRS datasets can take a while to validate. Have you attempted to run your validations on a full file GDB copy of the LRS? Try letting it run at the end of the day or overnight to see if it completes the Validation evaluation.

What is your map extent - are you evaluating the entire dataset? If you only want to evaluate the data in a specific area, you can limit it to the map extent before running your evaluations by clicking the Map Extent button on the Error Inspector window.

Are these custom Arcade Validations or are they Ready-to-use validations? If they are custom, you can perhaps optimize your code by using the filter function to reduce the amount of data being evaluated or by utilizing arrays and data dictionaries to trim down the data you are passing through to be evaluated.

Geometry checks can be time consuming. If you are using intersects, crosses, etc..., try to reduce the number of records that the Validation has to check. In Ready-to-use rules, you have the option to filter on attribute fields (TO_DATE is null).

I've found this video to be helpful in understanding how rules operate. Attribute Rules: A Deep Dive - Esri Videos: GIS, Events, ArcGIS Products & Industries