You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the results can contain an origin station that has no bikes, or a destination station that is completely full and cannot accept any more bikes. These kind of results are not useful for the user. The API should suggest some other stations instead - or walking if that is faster.
The text was updated successfully, but these errors were encountered:
The route planning results do take station emptyness into account, but you should still follow the situation in the UI and provide an alert whenever the route doesn't seem to be possible anymore. (When that happens, you can also make a request for new plans.) It can happen that all servers in the API cluster are not fully synchronized, which can cause these inconcistencies.
Ok. To be clear, the user made a routing request and that initial first result returned by the API was already invalid. Both the origin station was empty and the destination station was full. Are you saying this was caused by the servers in the API cluster not being fully synchronized?
Currently the results can contain an origin station that has no bikes, or a destination station that is completely full and cannot accept any more bikes. These kind of results are not useful for the user. The API should suggest some other stations instead - or walking if that is faster.
The text was updated successfully, but these errors were encountered: