An acquisition task may be needed to initiate the processing. The following example shows such a pattern where a wait task is created to check the presence of input data in the acquisition time window 10:00 to 12:00. A task is dedicated to raise a red alarm, by 11:00, if no data is not yet arrived, to have operators and analysts aware in advance to be careful about this. As soon as incoming data are detected, the data event is set, wait task shall sleep 60 seconds before completing, to ensure the server receives the event and starts the data task (validation and preprocessing). It will then set the ready event and acq family will become complete so that rt/wait and late_alert do not run any further.
family acq
complete acq/data eq complete
task data
trigger rt/wait:data
event ready
family rt
complete data:ready
task wait
event data
cron 10:00 12:00 00:05
endfamily
task late_alter
trigger not data:ready
time 11:00
endfamily