Can you try...cath the task code and send the notification on exception
base from the task it self, or make other kind of task that can be
schelude fron the first to send the notification in case of failure?
El vie., 6 jul. 2018 a las 5:51, Manuele Pesenti ()
escribió:
> Hi Dave,
>
> thanks for
On Friday, July 6, 2018 at 2:51:48 AM UTC-7, Manuele wrote:
>
> Hi Dave,
>
> thanks for your reply, I'm actually debugging but I found that the
> problem was a callback I added after scheduler_run update event in order
> to be advised by email for failed tasks.
>
> Is there a more correct way
Hi Dave,
thanks for your reply, I'm actually debugging but I found that the
problem was a callback I added after scheduler_run update event in order
to be advised by email for failed tasks.
Is there a more correct way of doing it? Maybe should be a good feature
for schduler.
Cheers
Ma
On Thursday, July 5, 2018 at 5:55:07 AM UTC-7, Manuele wrote:
>
> Hi!
>
> I'm in a trouble with the web2py (2.14.6 on python 2.7) scheduler that
> seams stop to run correctly... the tasks get the RUNNING status but
> nothing is performed and the task stay in the running status forever. I
> ca
Hi Niphlod,
thanks for your replay. I solved my trouble switching the scheduler db
connection that I forgot it was still using SQLite to PostgreSQL.
Thanks to this change the task has performed 2778 run from yesterday
evening without any problem.
Best regards
Manuekle
Il 21/05/15 18:35, Niph
On Thursday, May 21, 2015 at 6:13:56 PM UTC+2, Manuele wrote:
>
> Hi,
> I need a task that runs every 20" but ti seams that sometimes it gets
> more than the 19" I setup for the timeout.
>
set 18'' . it's a "python issue" that the timeout is not that precise-thing
to rely on. In their defens
6 matches
Mail list logo
