Any rule may have certain criteria.Status count: A number of the same status, within the time period. E.g. 10 errors within 10 minutes, 10 uploads, suspend the project.
Out of work.
e.g. If project X with application Y is active for more than 3 hours an event is triggered.
If project X with application Y generates 10 errors within 10 minutes an event is triggered.
If any task has a progress of less than 0.01% within 10 minutes an event is triggered.
If project X with application Y runs below 56C for xx time it will trigger an event.
SpecialsConnection is lost for xx time.
No work for xx time.
--------------------------------------------------------------------------------------------

It is possible to add a rule from the Tasks view. Click on the task you want add a rule for and press the right mouse key.
Select
Add ruleThis fills in all the names relevant for this task.
Rule name: Must be unique name that describes the rule.
Computer: Optional name of the computer, leave this empty if the rule applies to all computers.
Project: Optional name of the project, leave this empty if the rule applies to all projects.
Application: Optional name of the application, leave this empty if the rule applies to all applications.
* the above fields may hold a part of the name: Like 3.02, instead of the whole name.
Type:Cpu% The percentage between wall clock the actual run time of the CPU.
Elapsed Time The time the task has been running since the first start.
Progress % The progress percentage of the task.
Progress / min % As the Progress % but now the progress that has been made in one minute.
Temperature The CPU or GPU temperature. This rules must have a valid computer name.
Time left The time the task has left.
Use The number of CPU and GPU % that are planned for this task. E.g. 0.04 Cpu + 1 GPU or 0.025Cpu.
The 3 rules have to be ALL valid, at the same time for the event to trigger.
You may leave unused rules empty.
Time:The time the rule has to be valid to produce an event. Blank means 0 seconds.
Don't use a short time, as this may result in a lot of false positives.
Event:A rule may have one internal an one external event at the same time.
E.g. Suspend a task and start an external program.
A rule may have 0 events, so it only shows a color.
Run program Runs an external program or batch file.
The field below must hold the full name of the program. E.g. beep.bat
The folder is the default BoincTasks folder: C:\Users\user name\AppData\Roaming\eFMer\BoincTasks\
So beep.bat is the same as C:\Users\user name\AppData\Roaming\eFMer\BoincTasks\beep.bat
An ENTER (key) may be used to keep the text in the box.
You may add parameters: E.g. beep.bat, parameter
The "," is used to separate the program name from the parameter.
Suspend projectSuspends the project of the task that triggered the rule.
Suspend taskSuspends the task. When more tasks are triggered at the same time, only one is suspended. The other tasks are suspended, one every following second.
"show logging" check When checked, BoincTasks will show the rules logging window, when an event is triggered.
Resetting a rule:Rules are reset when you:
Edit any rule.
A tasks is no longer running.
Some inside information:The rules are checked, using the history information.
This means, the rules are checked, at the history interval time of about 12 seconds.
CPU % and Progress / min are measured, over a period of 2 cycles, about 24 seconds.