Had a strange bug today which I traced to multiple misconfigured Rules (and therefore they had all been disabled).
I would like to know how they become misconfigured as I can’t save a rule in that state, and none of the subset constraints have changed AFAIK.
All of the Rules that were misconfigured were related to a Remote Object “Task Template” if that helps in some way diagnosing the issue.
I note that the last update was by the system, not me? All of the misconfigured rules are updated by the system on Thu, 02 July 2026 …
Can anyone explain when a
system updated is applied….? Is this a snapshot install, an update, a patch???
I know I’ve done something wrong, but would like to figure what to stop this happening in the future.
Thanks for any help.
JonathanFS
Very intrigued by that system update and the correlation with the rules becoming misconfigured. If patches can bring about changes that lead to rules being misconfigured and disabled, it would be good to have that flagged somewhere easy to find. Does it show anything in the validator?
The “Misconfigured” status was introduced in 22.3 to help with identifying broken rules.
Previously, although the Validator Report would identify “broken” rules (e.g. they reference deleted or incompatible values), they would still show as active and might try to be executed (causing other issues).
Now the validator will flag them as Misconfigured status, and the system will no longer try to execute them.
In your case I imagine these rules were already broken, and this System change was simply them being flagged as Misconfigured to help indicate this.
When I examined the misconfgured rules, they are all configured correctly, no deleted constraints or missing subsets.
All I had to do to fix was save them…?
How are they misconfigured?
If you still have previous validation reports then that might give you the answers as to what was wrong at the time they were flagged.
Looking at the validator log, it is saying a subset was deleted….when it clearly was not.
It looks like some of my Rules lost visibility of the subsets? how can this happen.
Each of the Rules that was marked as misconfigured uses only 1 subset, and they have existed since 2025.
The update by me today, was me simply opening the subset and saving that to see if had zeroed out or something?
Thanks for you help Bob.
Yes that does seem confusing, someone would need to look directly at your app to be able to dig any deeper, so I’d raise a support request to that effect: Support - Netcall Community
