Skip to main content

Preferred charging networks makes planner error: 'oops...'

Bug Reports

Hello,

I’m trying to plan a route in France with quite a lot of constraints: no tolls, 3 different cards (Charge Map pass, Octopus Electroverse and Ulys) + Tesla member price and 3 charging networks selected (Tesla, NW IECharge and Lidl) has “douple thumbs up” (also tried “single thumbs up”).

When I try to plan the trip, it loads then trows an error “Oups… Quelque chose s’est mal passé” (Something went wrong).

I was able to get a 75% success-rate before when I only had Tesla and NW IECharge selected as preferred charging networks.

I am able to get a 100% success rate when no charging network preference is applied (at least with the 2-3 tries I did).


So my best guess is that there is a bit too much to process for the server and it times out just before finishing planning the trip. Server is the suspect to me because it happens both on my Google Pixel 6, or my quite powerful desktop.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by Thomas BORIE (Samoth47) ·
Status: Planned3 comments

Log in to comment and vote

Comments3

  • Bo (ABRP)

    Team•

    Mar 24, 2025

    Thank you for reporting, we see the crash in our logs and will fix it in the next ABRP release.

    • Thomas BORIE (Samoth47)

      •

      Mar 24, 2025

      Thanks for the quick response and (hopefully) fix!

      Have a great week

  • Thomas BORIE (Samoth47)

    •

    Mar 22, 2025

    The issue has evolved a bit, now I get this same error when I open the app or the web page the first time. I've looked a bit at the responses given by the server, it seems to work correctly (200 HTTP response with full data), but the data it returns may not be correct to the frontend, throwing an error. That's probably why it crashes when opening the app / web page: it tries to load the previous planned path but fails because the data is still incorrect.