Hello Joe, I am not using the scheduler primarilly because I never had time to implemented it. But I miss so much all the things you mention... Let says just configure a task to lock a user account on a specific date in the future when you have employee termination in advance and you have no other proper mean to recall that and don't want to pollute your calendar with a bunch of todo thing...
The only flaw I see is relying on the tool and having some task not performed as expect for some reason and not get properly inform that a given task didn't succeed as expect... Depending of the criticallity of the task this may have bad consequences... Richard On Mon, Jun 11, 2018 at 11:16 AM, Anthony <abasta...@gmail.com> wrote: > I suppose that should be fine. Tasks are stored in a database, so should > be as durable as any other data you are storing. > > Alternatively, you might consider storing the reveal date with the item > and running a regular task that simply selects all items with reveal dates > equal to or earlier than the current day and updates those items to become > visible. Or even just add a common filter that automatically filters out > any records with a future reveal date. > > Anthony > > > On Sunday, June 10, 2018 at 7:20:19 PM UTC-4, Joe Barnhart wrote: >> >> Are there any reasons I should not schedule tasks days, weeks, or months >> in advance in the web2py scheduler? It seems such a fantastic, >> general-purpose tool that I'm using it for more and more things in the >> site. >> >> Currently I'm considering using it to "reveal" embargo'ed items that >> should not be seen until a certain date and time. The reveal would involve >> putting a task in the scheduler for the far-away date and having it create >> a permission on a table at the moment of truth. >> >> Is there some reason this might be considered bad design, or poor use of >> the scheduler? Reliability is of high importance in my site, so design >> that decreases reliability is to be avoided. >> >> -- Joe >> >> -- > Resources: > - http://web2py.com > - http://web2py.com/book (Documentation) > - http://github.com/web2py/web2py (Source code) > - https://code.google.com/p/web2py/issues/list (Report Issues) > --- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to web2py+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
