This error occurs when the optimizer returns no superchargers. In fact though while it did not find any, it did not need any either.
So the app needs to ensure that before the error is displayed that the energy needs were not already met. Then if the energy needs are not met it can display the error.
I think this was a bug in the old server routing program. A new trip that required no charging stops worked just fine with no errors. Tested in V1.2 (34).
This error occurs when the optimizer returns no superchargers. In fact though while it did not find any, it did not need any either.
So the app needs to ensure that before the error is displayed that the energy needs were not already met. Then if the energy needs are not met it can display the error.