If you experience BES Server based automation running multiple times where you only were expecting it to fire once then it could simply be a configuration problem!
There are two possible causes
- The automation was defined to run on both New and Updated alerts. If the automation fired from a new alert actually updates the calling alert during the automation activity this could cause the automation to fire again and in extreme conditions cause an infinite loop!
- The automation has been defined under one or more login groups. The automation will fire for each group that it has been defined for.
You can check the $PPLOG/UserAO_Log to see manual and automated instigation of automation.
- Ensure you're automation is correctly set for New, Updated or New and Updated alerts.
- Ensure your automation has only been defined in the one group. The automation definitions exist in ASCII files on the BES server under $PPHOME/eScape/htdocs/ppwc/applets/group/Automation_[GROUPNAME]