Re: [WebDNA] triggers.db "next execute" fails to update

This WebDNA talk-list message is from

2012

It keeps the original formatting. numero = 108340
interpreted = N
texte = > [snip] Nevertheless I need the problem=20> fixed, so I'll have to figure this out myself, hopefully with=20> some bright ideas from others here.>=20> Any idea why WebDNA might fail to update the "next execute"=20> value when the trigger is run?*perhaps* it's a bug?from the other day:> Yes. =20> And for the life of us we could not discover why the trigger code was =executing more often than we have told it to.> The only way to "stop" it was to wrap the code in a conditional that =checks the [time] string.. and requires a time that is in congruity with =when we told Webdna to hit the trigger. So for all I know the trigger =is still being hit every half hour (that was how often it was being hit =for some unknown reason, even though we told it to be hit only once per =day), but the email it generates is now only being generated once per =day.. as per the conditional wrapper that we added in that file.>=20> Seems to be bug week. Everyone hang in there ;-)>=20> -G Associated Messages, from the most recent to the oldest:

Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update ("Psi Prime Inc, Matthew A Perosi " 2012)
Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update ("Psi Prime Inc, Matthew A Perosi " 2012)
[BULK] Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
Re: [WebDNA] triggers.db "next execute" fails to update (Stuart Tremain 2012)
Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
[BULK] Re: [WebDNA] triggers.db "next execute" fails to update (Donovan Brooke 2012)
Re: [WebDNA] triggers.db "next execute" fails to update (sal danna 2012)
Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
Re: [WebDNA] triggers.db "next execute" fails to update (Rob 2012)
Re: [WebDNA] triggers.db "next execute" fails to update (Govinda 2012)
Re: [WebDNA] triggers.db "next execute" fails to update (William DeVaul 2012)
[WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)

> [snip] Nevertheless I need the problem=20> fixed, so I'll have to figure this out myself, hopefully with=20> some bright ideas from others here.>=20> Any idea why WebDNA might fail to update the "next execute"=20> value when the trigger is run?*perhaps* it's a bug?from the other day:> Yes. =20> And for the life of us we could not discover why the trigger code was =executing more often than we have told it to.> The only way to "stop" it was to wrap the code in a conditional that =checks the [time] string.. and requires a time that is in congruity with =when we told Webdna to hit the trigger. So for all I know the trigger =is still being hit every half hour (that was how often it was being hit =for some unknown reason, even though we told it to be hit only once per =day), but the email it generates is now only being generated once per =day.. as per the conditional wrapper that we added in that file.>=20> Seems to be bug week. Everyone hang in there ;-)>=20> -G Govinda

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] triggers.db "next execute" fails to update

2012

Top Articles:

Related Readings: