I want to make you aware I corrected my previous post on On Demand Detections. I must thank Pete Zerger of SystemCenterCentral, he pointed out cookdown is working between rules and monitors. He was referring to this sentence of mine:
cookdown seems to work for workflow type, it cooks for monitors and cooks for rules but not across the two this is why I have two S1 runs at sync time when I have both monitors and rules even if they’re time synced
the statement above implies we can have race conditions between monitors and rules when they use the same data source / provider and they’re time synced
This proved to be incorrect but it took a long to understand while I was observing this behavior. I indeed had two runs one for rule and one for monitors but because monitors had the ConfirmDelivery property set to false, while the rule had it set to true (it has been a copy and paste error). This makes the HS split the datasource in two and in fact I have two copies of the script on the file system. Now the above sentence has been corrected as follows:
This posting is provided "AS IS" with no warranties, and confers no rights.