Deamon.g execution wait time to handle event triggers

[presto]

The current wait time for RRF to execute daemon.g file is 10 seconds. I have the following code in daemon.g with the global variables declared in config.g

;daemon.g

while {global.alert} = 1
	M42 P30 S0.2 	; beeper on
	G4 P100		; wait 200ms
	M42 P30 S0.8 	; beeper on
	G4 P100		; wait 200ms
	M42 P30 S0 	; beeper off
	G4 S1		; delay 1 second

while {global.warning} = 1
	M106 P9 S255	; LED 1 on
	M106 P10 S255	; LED 2 on
	M42 P30 S0.7 	; beeper on
	G4 P100		; delay 100ms
	M106 P9 S0	; LED 1 off
	M106 P10 S0	; LED 2 off
	M42 P30 S0 	; beeper off
	G4 P100		; delay 100ms

For example with an event, let's say a filament runout event that will send,

set global.alert = 1

It will potentially take up to 10 seconds for the command in daemon.g to execute even though it is in a while loop. Before RRF 3.3 the wait time was 1 seconds which is ideal but may potential take up precious computing resources. Is there anyway for a user to decrease the wait time? Or even better for it to be a configurable amount of time in gcode or Duet Web Control for future RRF and DWC releases.

[jay_s_uk]

@presto put them in a loop so something like

while true
  while {global.alert} = 1
...

then they will run continuously