Skip to main content

Ignoring next day departure time

Bug Reports

The ABRP planning process is ignoring next day departure time and continuing as if same day on one particular waypoint. Waypoint is reached at 5:48 PM on 7/23. I have manually set departure time at the waypoint (which is an Airbnb) for 7/24 9:00 AM. ABRP is ignoring that and proceeding as if it is on the same day, taking departure time same as arrival time of 5:48 PM

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by Niladri Roy ·
Status: Completed4 comments

Log in to comment and vote

Comments4

  • Katya S. changed status to Awaiting Clarification
    Team•

    Jun 24, 2025

    Pinned

    Hi,

    Please provide a link to the plan where this occurs. To do this;

    1. Plan the trip in ABRP

    2. Click/tap: ‘Share plan’

    3. Click/tap: ‘Share ABRP link’

    4. Paste the URL here

    ⚠️ IMPORTANT: Please exclude private addresses and the use of ‘my position’, home, work, etc., from the plan you post here publicly.

    • Niladri Roy

      •

      Jun 24, 2025

      I am posting the URL below, as requested. I have removed the starting home address and replaced it with city name. There is another residential address in the plan, but that is an Airbnb and is public information to anyone using the Airbnb app.

      I draw your attention to the entry just before the Tesla supercharger at Eureka, CA. That entry is the Airbnb waypoint that we are talking about. You will find that the departure from here has been manually set by me for 9:00 AM the next day, but that info is currently being ignored by ABRP.

      https://abetterrouteplanner.com/?plan_uuid=c9459a35-1fd6-4314-8892-d5eacef359b9

      [1. Please pardon the many waypoints for ‘Avenue of the Giants'. If I don’t do that, ABRP keeps returning me to Hwy 101, which I do not want. This is likely a low-priority bug as well.
      2. Note that ABRP has no problems in picking up next-day-departure if it sees keywords like Hotel, Motel, Inn, Lodge etc in a waypoint, but has problems with the Airbnb address which has no such keyword. My humble suggestion would be to examine your code to see if departure-time actually does not work, and a circumventing shortcut is being employed using keywords - just throwing out a “maybe” here.]

    • Niladri Roy

      •

      Jun 24, 2025

      I apologize - this has now been resolved. It is possible that I had inadvertently set one of the earlier waypoint departure dates to 7/24 instead of 7/23. ABRP is now correctly picking up the next day departure. I regret the inconvenience caused,

  • ABRP User #1949698

    •

    Aug 28

    Thought I’d add a tip here to anyone still encountering the same problem. If you are using an old saved trip, manually re-entering the waypoints and letting the route planner re-plan from scratch will resolve the issue.