[null,null,["最后更新时间 (UTC)：2025-08-31。"],[[["\u003cp\u003eFleet Engine's \u003ccode\u003eSearchTripsRequest\u003c/code\u003e helps find trips, useful for identifying active trips and reconciling vehicle availability.\u003c/p\u003e\n"],["\u003cp\u003eUse \u003ccode\u003eSearchTripsRequest\u003c/code\u003e with \u003ccode\u003evehicle_id\u003c/code\u003e and \u003ccode\u003eactive_trips_only\u003c/code\u003e to find a specific vehicle's active trips.\u003c/p\u003e\n"],["\u003cp\u003eDiscrepancies between your system and Fleet Engine's vehicle availability can be addressed by using \u003ccode\u003eSearchTripsRequest\u003c/code\u003e to identify open trips and ensure trip statuses are synchronized.\u003c/p\u003e\n"],["\u003cp\u003eTrips older than 7 days are automatically deleted in Fleet Engine.\u003c/p\u003e\n"]]],["The `SearchTripsRequest` endpoint in Fleet Engine allows finding trips, focusing on two scenarios. First, setting `vehicle_id` and `active_trips_only` to `true` identifies active trips for a specific vehicle. Second, to reconcile vehicle availability, `vehicle_id` is left empty, `active_trips_only` is `true`, and `minimum_staleness` is set to over an hour. This identifies open, outdated trips (neither `COMPLETE` nor `CANCELED`) for status reconciliation. Trips are only searchable for seven days.\n"],null,["Fleet Engine provides the `SearchTripsRequest` endpoint that you can use to find\ntrips. This document describes two scenarios where you might use this feature.\n\nSee `SearchTripsRequest` for [gRPC](/maps/documentation/mobility/fleet-engine/reference/trips/rpc/maps.fleetengine.v1#searchtripsrequest) or `trips.Search` for [REST](/maps/documentation/mobility/fleet-engine/reference/trips/rest/v1/providers.trips/search).\n| **Note:** Trips remain active in Fleet Engine for 7 days, after which they are deleted, so `SearchTrips` only shows trips that have been active within the past 7 days.\n\nDetermine active trips for a vehicle\n\nTo do find the active trips for a specific fields, use the `SearchTripsRequest`\nmessage to set the `vehicle_id` to the vehicle under consideration and set\n`active_trips_only` to `true`.\n\nReconcile vehicle availability between your system and Fleet Engine\n\nIn some situations, you might see results returned by `SearchVehicles` that\ndon't correspond with the vehicles you know to be available in your system and\nyour fleet. This happens because `SearchVehicles` either doesn't show vehicles\nwith active trips, or pushes them down in the results ranking. One cause of this\nis when vehicles have completed trips, but the trip status not been properly set\nto either `COMPLETE` or `CANCELED`. By using `SearchTrips` to find open trips,\nyou can evaluate vehicles to ensure that `TripStatus` in your system matches\nthat of Fleet Engine.\n\nTo use `SearchTrips` in this way, set the following in the `SearchTripsRequest`\nmessage:\n\n- `vehicle_id` should be empty.\n- `active_trips_only` should be `true`.\n- `minimum_staleness` should be a time greater than most trip durations; for example, one hour.\n\nThe results of such a request include Trips that are neither `COMPLETE` nor\n`CANCELED`, and have not been updated in over an hour. You can then examine\nthese trips to ensure that their status in Fleet Engine is properly updated.\n\nWhat's next\n\n- [Delete Trip](/maps/documentation/mobility/fleet-engine/journeys/trips/delete-trip)"]]
