...
Note3: It is recommended to set the interval to 1 second if the action should be executed for every event code (e.g. in the case of sending alert messages), but should be increased if it is not desirable to execute several workflows in a short period (e.g. the case of creating web reports). It also needs the "template task" with the relevant tag scheduled (in suspended mode) as a single/one-off task.
Dual MC failover with runOnFailOver
Since 2015.01 suspended one-off tasks can be triggered by failover (both manual and automatic failover).
For instance when the duty master-controller has a suspended one-off task prepared which is available via MC-Synchronisation at the other MC, then the second MC can trigger the duty Mc's task when a similar event-action mapping is available in the second MC.
E.g. MC00 is the duty MC and MC01 the backup. On both MCs there are frequently running import tasks both generating TASKRUN:Complete.ImportExternal. One suspended task one-off task BigCalculation has been prepared at the MC00 with the runOnFailOver option active.For MC01 no such task is prepared.
1. When MC00 is running fine, only MC00 triggers the BigCalculation task, MC01 logs that an event is processed but could not find a task.
2. MC00 is put in manual failover -> both MC00 and MC01 trigger BigCalculation task.
3. MC00 is restored from manual failover -> only MC00 triggers BigCalculation task.
4. MC00 is brought down -> only MC01 triggers BigCalculation task.
5. MC00 is restarted -> only MC00 triggers BigCalculation task.
6. MC00 is brought down by shutting down all FSSs -> only MC01 triggers BigCalculation task.
7. all MC00 FSSs are restarted-> only MC00 triggers BigCalculation task.
Related information on Event-codes
...