Here are some common errors that can occur during trip monitoring:

HTTP RPC Description
400 INVALID_ARGUMENT Client specified an invalid trip name. The trip name must follow the format providers/{provider_id}/trips/{trip_id}. The provider_id must be the ID of the Cloud Project owned by the service provider.
401 UNAUTHENTICATED You receive this error if there are no valid authentication credentials. For example, if the JWT token is signed without a trip ID or the JWT token has expired.
403 PERMISSION_DENIED You receive this error if the client does not have sufficient permission (for example, a user with the consumer role tries to call updateTrip), if the JWT token is invalid, or the API is not enabled for the client project. The JWT token might be missing or the token is signed with a trip ID that does not match requested trip ID.
429 RESOURCE_EXHAUSTED The resource quota is at zero or the rate of traffic exceeds the limit.
503 UNAVAILABLE Service unavailable. Typically the server is down.
504 DEADLINE_EXCEEDED Request deadline exceeded. This error only occurs if the caller sets a deadline that is shorter than the method's default deadline (that is, the requested deadline is not enough for the server to process the request) and the request did not finish within the deadline.