Skip to main content
I have a customer who had the "Task" object removed from the rules configuration page (Admin > Rules > Gear Icon). In this scenario, it didn't delete the setup action.... but the rule itself stopped working. If you'd click on the setup action and try to save it... it would wipe out the rule (per design). Once we identified what happened and restored the task object back into the field permission list, the rule was restored to its original working state. 





The issue, however, is that this rule ran successfully for quite some time until someone noticed that it wasn't producing any results. There were no notifications to the admin that this situation had happened. The customers concern is that if this happens again, it could be even longer before someone notices that it is not working. Is there a way that we can fail a rule in this scenario so the user isn't under the impression that the rule is running successfully with out any failure notifications?
Thoughts


1) Should we notify as a potential error state is rule running with no actions . (Steve - were there any other actions in that rule)





2) On the permissions, seems we are missing a dependency check that says - you have rules defined that require this.  We do this elsewhere but seems a spot where this is needed
We should be failing the rule with right error message. You can file this a bug, I'll get this fixed.
This was fixed long time back. When a object is removed from the "Permissions - Rules Loadable Object" page then we are failing the rule. We can find Error message as 'Invalid Target Object/Field' in the Execution Logs.





Above behaviour is same even if just one field that used in Action mapping is removed for the Permissions page.





Hope, this helps!

Reply