In a utility network, I have a batch attribute rule on a table with type data for cables. When the rule runs, all updated types will have some of its' properties copied to cables using the specific type. But when running/evaluating the rule for the first time, I believe it sees every type as changed and wants to update all cables. I get error 999999 "Something unexpected caused the tool to fail" after 10 minutes. If I run the rule async, it errs after 2 hours. This leads me to believe it is the amount of data being updated that causes a timeout.
Is there any way to mark all rows in the table as "OK, nothing has changed", so only future changes to the table will be caught by the batch attribute rule being run?
Or is there any other way to have the initial run be successful?
