Re: [WebDNA] triggers executed at boot instead of scheduled time

This WebDNA talk-list message is from

2011

It keeps the original formatting. numero = 107174
interpreted = N
texte = Hi Steve,As mentioned in the trigger admin:"The trigger will execute if it is enabled, and the NextExecute timeis earlier than the current time"My guess is that the NextExecute had passed while your server was having issues..Anyway,I don't like to rely on triggers to run code at certain times.Instead, I wrap my code to be fired in a "time wrapper"..ie. (code to be ran once daily)-----------------------------------------------------------[if ({[time]} < {sometime}) & ({[time]} > {sometime})] [then] [!] ** Some solution to know if already hit today ** [/!] [text]t_lasthit=[lookup db=codehit.db&lookinfield=ch_date&value=[date]&returnfield=ch_id¬found=NF] [showif [t_lasthit]=NF] < Run your code > [!] ** record hit ** [/!] [append db=codehit.db&autonumber=CH_ID]ch_date=[url][date][/url][/append] [/showif] [/then][/if]------------------------------------------------------------Then set up a trigger that fires every minute or so.. enough topass the initial condition a few times (for redundancy).Hope that helps to avoid future problems.Donovan-- Donovan BrookeEuca Design Center[Practical-Ethical-Efficient]www.euca.usegg.bzartglass-forum.com Associated Messages, from the most recent to the oldest:

Re: [WebDNA] triggers executed at boot instead of scheduled time ( 2011)
Re: [WebDNA] triggers executed at boot instead of scheduled time (Steve Raslevich - Northern Sound 2011)
Re: [WebDNA] triggers executed at boot instead of scheduled time (Donovan Brooke 2011)
[WebDNA] triggers executed at boot instead of scheduled time (Steve Raslevich - Northern Sound 2011)

Hi Steve,As mentioned in the trigger admin:"The trigger will execute if it is enabled, and the NextExecute timeis earlier than the current time"My guess is that the NextExecute had passed while your server was having issues..Anyway,I don't like to rely on triggers to run code at certain times.Instead, I wrap my code to be fired in a "time wrapper"..ie. (code to be ran once daily)-----------------------------------------------------------[if ({[time]} < {sometime}) & ({[time]} > {sometime})] [then] [!] ** Some solution to know if already hit today ** [/!] [text]t_lasthit=[lookup db=codehit.db&lookinfield=ch_date&value=[date]&returnfield=ch_id¬found=NF] [showif [t_lasthit]=NF] < Run your code > [!] ** record hit ** [/!] [append db=codehit.db&autonumber=CH_ID]ch_date=[url][date][/url][/append] [/showif] [/then][/if]------------------------------------------------------------Then set up a trigger that fires every minute or so.. enough topass the initial condition a few times (for redundancy).Hope that helps to avoid future problems.Donovan-- Donovan BrookeEuca Design Center[Practical-Ethical-Efficient]www.euca.usegg.bzartglass-forum.com Donovan Brooke

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] triggers executed at boot instead of scheduled time

2011

Top Articles:

Related Readings: