"Next execution" for tasks are at a passed time, tasks are not triggered.

[gandalfgray]

Hi

After a restart of the central node where the Qlik services did not start properly by themself but started later,

we have the situation that the task scheduling does not work as it should.

Lots of tasks have "Next execution" set at a time that has already passed and are not started.
See attached screenshot which was taken 2018-07-19 09:07,

there are lots of tasks with "Next execution" at 2018-07-18...

This is the third or fourth time this happens for us.
Last time it was solved by restarting all Sense servers, but that did not help this time.

We are using November 2017 patch 3 and have six nodes in the cluster

(and yes, the time on all the servers are correct)

Anyone else had this problem and now have to fix it?

Screenshot at 2018-07-19 09:07

[micheledenardi]

I've the same issue, how did you resolve ?

Thanks