[Jason Wilder]

Sorry wrong Subject for this post and I can’t seem to change it, should say NAV 2018 Task Scheduler “Earliest Start DateTime”.  I do have deadlocking issues with task scheduler but that will be a separate post.

We are on NAV 2016 and in the process of upgrading to NAV 2018.  The upgrade is done(ish) and we are beginning our testing. I have poured through the new structure for task scheduler and job queue entries and have a pretty good feel of how it works behind the scenes.  We have about 150 recurring job queue entries (posting invoices, settling cc batches, integrations, etc…).  Here is my first of a few issues with Job Queue Entries running through Task Scheduler:

The “Earliest Start Date/Time” doesn’t do a good job for job queue entries in the past (this behavior was in NAV 2016 as well which I fixed but didn’t carry my fix over to NAV 2018 yet).  For example, lets say I have 4 entries that should run at midnight every night.  When I turn task scheduler on for the first time it resets the Earliest Start Date/Time to the Current DateTime so it totally loses the original midnight time and now is on a different schedule completely.  Does anyone else experience this when your jobs have an “Earliest Start DateTime” in the past?

——————————
Jason Wilder
Senior Application Developer
Stonewall Kitchen
York ME
——————————

[Meenakshi Singh]

Hi Jason,
I have experienced the same issue in NAV2018. My resolution is to change the earliest start date/time to what we want it to be after the RESET.  I see how that can be a problem in your case with so many entries. I would be curious to know if someone has a better resolution for it.

~Meenakshi

——————————
Meenakshi Singh
Manager of Business Applications
Home Market Foods, Inc.
Norwood MA
——————————
——————————————-