(Migrated) Scheduled jobs stop working

(This message has been automatically imported from the retired mailing list)

I have a problem with scheduled jobs that stops running at the times where =
I expect them to.

When I try to execute such a job manually through the scheduler page in adm=
in I get this log message:

Job […] is not scheduled, could not execute it

But the job is marked active in the scheduler. Then, if I deactivate the jo=
b and activate it again, I can execute it trough the admin and now it also =
seems the run and the scheduled times - but sooner or later it will stop ag=
ain.

Finn Gruwier Larsen

Forbrugerr?det Taenk er en uafhaengig medlemsorganisation, der arbejder for=
et Danmark, hvor alle forbrugere kan traeffe et trygt valg.
F? nyheder, informationer om test, tilbud og gode r?d 1-2 gange om ugen. Ti=
lmeld dig vores nyhedsbreve p? taenk.dk/nyhedsbrev

Fra: Zato-discuss [mailto:zato-discuss-bounces@lists.zato.io] P=E5 vegne af=
Finn Gruwier Larsen
Sendt: 15. august 2014 09:30
Til: zato-discuss@lists.zato.io
Emne: [Zato-discuss] Scheduled jobs stop working

I have a problem with scheduled jobs that stops running at the times where =
I expect them to.

When I try to execute such a job manually through the scheduler page in adm=
in I get this log message:

Job […] is not scheduled, could not execute it

But the job is marked active in the scheduler. Then, if I deactivate the jo=
b and activate it again, I can execute it trough the admin and now it also =
seems the run and the scheduled times - but sooner or later it will stop ag=
ain.

Finn Gruwier Larsen

I have an update on this. The problem seems to appear when Zato has been re=
started. I also now remember that I have had this issue before - but unfort=
unately I don’t remember the solution.

Finn Gruwier Larsen

On 15/08/14 10:48, Finn Gruwier Larsen wrote:

I have an update on this. The problem seems to appear when Zato has been
restarted. I also now remember that I have had this issue before - but
unfortunately I don’t remember the solution.

Hi Finn,

the only sure way to resolve it is to upgrade to a recent git master
version.

The scheduler has been completely rewritten from scratch several weeks
ago and what you describe is one of the things that has been improved.