Job does not run when scheduled

[maxslabyak]

If I schedule a publish at a specific time, I see it taking sometimes anywhere from 10-30 mins to actually run.

[RosenPetrov]

Hello Max,
The current version uses the Sitecore scheduling implementation. Sitecore.Tasks.DatabaseAgent runs every 10 minutes (without any relation to a particular time). Depending on the value in the Last Run field, the agent decides whether or not to execute the Scheduled Publish Task. This means that you should expect a time margin between the exact scheduled time and the execution. The ASP.NET architecture makes it unrealistic to expect to invoke a process at a very specific time. We could consider adding support for the Windows Task Scheduler, which would get around these limitations, in the next version. We are also open for any suggestions for improvements in this direction.
Thanks for your feedback. It's appreciated.

[maxslabyak]

"Depending on the value in the Last Run field, the agent decides whether or not to execute the Scheduled Publish Task. "
What would be the case(s) where it would decide not to execute?

On Tue, Jul 5, 2016 at 4:30 AM -0400, "Rosen Petrov" [email protected] wrote:

Hello Max,

The current version uses the Sitecore scheduling implementation. Sitecore.Tasks.DatabaseAgent runs every 10 minutes (without any relation to a particular time). Depending on the value in the Last Run field, the agent decides whether or not to execute the Scheduled Publish Task. This means that you should expect a time margin between the exact scheduled time and the execution. The ASP.NET architecture makes it unrealistic to expect to invoke a process at a very specific time. We could consider adding support for the Windows Task Scheduler, which would get around these limitations, in the next version. We are also open for any suggestions for improvements in this direction.

Thanks for your feedback. It's appreciated.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[spareva]

Hi Max,
It would not execute if it is not time for it to do so yet, i.e. the amount of minutes described in the web.config has not passed yet. In a default scenario of a 10-minute check in the web.config the maximum logical delay possible would be 19 minutes 59 seconds. Any builds, config changes or other actions that would cause a Sitecore/IIS restart could cause a further delay.

Thanks,
Svetlana