Termination request

Termination request are used to mark trips at a point in time that a request has been made, thus allowing to define a precise date to end the trip.

What are termination requests

A termination request is an object belonging to a trip. It can be created internally by our system, or externally by a cyclist. Those are two specific workflow and are used in two differents contexts.

How they work

Termination request status is directly linked to its trip status. The following schema explain the workflow of termination requests and how their creation actively change the trip status until its completion.

Note

Blue square are the trip’s status

If the cyclist has just returned the vehicle to a station, but the area in which the station is located has no network coverage, the vehicle can’t communicate with our servers, and the vehicle displays an error message.

In this case, if nothing is done, the trip timer continues to run, and the cyclist risk being overcharged. It’s in this specific case that the cyclist can make a termination request from his application, by sending in addition a picture of the vehicle locked on the station.

The trip will be completed when the vehicle will be rented again, or if the operator closed it from his dashboard, with the terminated date of the cyclist request.

Note

accepted termination requests are always initiated by the system.

pending termination requests are always initiated by a cyclist.

When the trip is completed, the trip’s termination date is set to the oldest not cancelled termination request.