While looking at the run History for the process we see that it dutifully runs at 2AM (GMT) as expected on Saturday (which is the Friday 10PM (EST) Run)
However then it Skips the 2AM on 5/17 (Sunday) which would be a Saturday 10 PM (EST) Run My guess is because we told it not to run on Sunday
It appears that it is doing the Day of the Week check on GMT time, while running the schedule instead of converting it to EST before checking which causes it to run on the wrong day of the week
CASE: CS0002048210
Epicor Version: 10.2.300.12
@JeffLeBert I hear this one may be up your alley? Any insights?
This is âup my alleyâ even though Iâm playing in other areas now.
I remember seeing this and thinking it was wrong, but was so deep in other areas, that I couldnât investigate fully. I donât recall exactly what the little investigation I did found. I think it is 100% correct to store the date/time as
UTC. My first âmajorâ work in Task Agent was in 10.2.500 so I would have been trying to keep things compatible, even if odd. I vaguely remember the problem was in the UI itself.
The good news is that you can adjust your time so that it will be 10PM. This sucks, but should work fine. Maybe submit a bug to Epicor? Youâve already documented the issue beautifully.
I donât think the issue is that itâs not running at the time the UI says. But rather the Day of the week is off, when the time displayed on the UI is before midnight, and itâs UTC equivalent is after.
Thanks Jeff I was just throwing it here for documentation and to inform others. I opened a case with support and hopefully it will escalate (eventually when I explain it to them 14 times lol)
Weâve made the correction on our side this is really only an issue if you are
a) skipping a day
b) && the time of the schedule drives GMT into the next day
So very specific conditions that we just so happen to hit⌠To the tune of $200K (attributed to the wrong financial period) but weâll manage for now.
And it is reported.
Thank @ckrusen, that got some neurons firing again. That does sound like what I found when I looking at this. If I remember correctly, the time is in UTC and the days basically are not.
The UI fix would be fairly easy. It would be hard to migrate the existing schedules because we donât know the time zone the user was in, so we couldnât determine if the days in the schedule were correct or a day off either way. I guess, you would use the time zone from where you were doing the migration and be pretty close.
Darn it @JasonMcD if you had put in a ticket the ETA may be ~500 and maybe I would have missed being wounded⌠oh wait Iâm still in 300⌠but itâs the principle that matters!
