The same exact route, date, time and config yields different results depending on when I use ABRP.

🚧 THIS IS A TICKET MIGRATED FROM UPVOTY. The original ticket and comments will be available for a limited time over at:
https://abrp.upvoty.com/b/report-a-bug/the-same-exact-route-date-time-and-config-yields-different-results-depending-on-when-i-use-abrp/
———————————————————————————
I have a route with a starting point, destination and waypoints set up with specific dates and times set for each of them: the departure, arrival and time spent at each of the way points, including specific arrivala and departure times for some of the way points. I also have some car, battery, vehicle (weight), and road conditions (headwind) config set up.

What I have consistently found is that I see very different results from ABRP for the recommended route plan and charging stops etc. depending on what time of the day I use ABRP. I am in the Pacific TZ. If I use ABRP in the daylight hours, e.g. 11 AM or 2 PM Pacific, I get a route that is feasible, it even adjusts the route plan if I change the vehicle weight, battery and road conditions (headwind) config, and that is expected and all good. However when trying to generate a plan for exact same route and config no changes whatsoever, but use the ABRP site at night, around 11 PM pacific time, I get a result from ABRP that says there is no valid route possible with dotted lines and red lines etc on the recommended route.
Quite bizarre. Am I missing something here? I would assume that if you have specific departure dates and times and arrival dates and times set, config set, what time of day or night you use the ABRP software should not impact where there is a route available or not.

Using ABRP on chrome Version 104.0.5112.101 (Official Build) (x86_64) on MacOS 13.0 Beta (22A5321d).