@@ -276,18 +276,21 @@ public ComputeFlightEmissions set(String parameterName, Object value) {
276276 * cascading logic (using the first one that is available): 1. TIM-based emissions given origin,
277277 * destination, carrier, flightNumber, departureDate, and cabinClass. 2. Typical flight emissions
278278 * given origin, destination, year in departureDate, and cabinClass. 3. Distance-based emissions
279- * calculated using distanceKm, year in departureDate, and cabinClass. If there are no estimates
280- * available for a certain flight with any of the three methods, the response will return a
281- * Scope3FlightEmissions object with empty emission fields. The request will still be considered
282- * successful. Generally, missing emissions estimates occur when the flight is unknown to the server
283- * (e.g. no specific flight exists, or typical flight emissions are not available for the requested
284- * pair). The request will fail with an `INVALID_ARGUMENT` error if: * The request contains more
285- * than 1,000 flight legs. * The input flight leg is missing one or more identifiers. For example,
286- * missing origin/destination without a valid distance for TIM_EMISSIONS or TYPICAL_FLIGHT_EMISSIONS
287- * type matching, or missing distance for a DISTANCE_BASED_EMISSIONS type matching (if you want to
288- * fallback to distance-based emissions or want a distance-based emissions estimate, you need to
289- * specify a distance). * The flight date is before 2019 (Scope 3 data is only available for 2019
290- * and after). * The flight distance is not between 0 and 25,000,000,000,000,000 km. * Missing cabin
279+ * calculated using distanceKm, year in departureDate, and cabinClass. If there is a future flight
280+ * requested in this calendar year, we do not support Tier 1 emissions and will fallback to Tier 2
281+ * or 3 emissions. If the requested future flight is in not in this calendar year, we will return an
282+ * empty response. We recommend that for future flights, computeFlightEmissions API is used instead.
283+ * If there are no estimates available for a certain flight with any of the three methods, the
284+ * response will return a Scope3FlightEmissions object with empty emission fields. The request will
285+ * still be considered successful. Generally, missing emissions estimates occur when the flight is
286+ * unknown to the server (e.g. no specific flight exists, or typical flight emissions are not
287+ * available for the requested pair). The request will fail with an `INVALID_ARGUMENT` error if: *
288+ * The request contains more than 1,000 flight legs. * The input flight leg is missing one or more
289+ * identifiers. For example, missing origin/destination without a valid distance for TIM_EMISSIONS
290+ * or TYPICAL_FLIGHT_EMISSIONS type matching, or missing distance for a DISTANCE_BASED_EMISSIONS
291+ * type matching (if you want to fallback to distance-based emissions or want a distance-based
292+ * emissions estimate, you need to specify a distance). * The flight date is before 2019 (Scope 3
293+ * data is only available for 2019 and after). * The flight distance is 0 or lower. * Missing cabin
291294 * class. Because the request is processed with fallback logic, it is possible that misconfigured
292295 * requests return valid emissions estimates using fallback methods. For example, if a request has
293296 * the wrong flight number but specifies the origin and destination, the request will still succeed,
@@ -323,19 +326,22 @@ public class ComputeScope3FlightEmissions extends TravelImpactModelRequest<com.g
323326 * cascading logic (using the first one that is available): 1. TIM-based emissions given origin,
324327 * destination, carrier, flightNumber, departureDate, and cabinClass. 2. Typical flight emissions
325328 * given origin, destination, year in departureDate, and cabinClass. 3. Distance-based emissions
326- * calculated using distanceKm, year in departureDate, and cabinClass. If there are no estimates
327- * available for a certain flight with any of the three methods, the response will return a
328- * Scope3FlightEmissions object with empty emission fields. The request will still be considered
329- * successful. Generally, missing emissions estimates occur when the flight is unknown to the
330- * server (e.g. no specific flight exists, or typical flight emissions are not available for the
331- * requested pair). The request will fail with an `INVALID_ARGUMENT` error if: * The request
332- * contains more than 1,000 flight legs. * The input flight leg is missing one or more
333- * identifiers. For example, missing origin/destination without a valid distance for TIM_EMISSIONS
334- * or TYPICAL_FLIGHT_EMISSIONS type matching, or missing distance for a DISTANCE_BASED_EMISSIONS
335- * type matching (if you want to fallback to distance-based emissions or want a distance-based
336- * emissions estimate, you need to specify a distance). * The flight date is before 2019 (Scope 3
337- * data is only available for 2019 and after). * The flight distance is not between 0 and
338- * 25,000,000,000,000,000 km. * Missing cabin class. Because the request is processed with
329+ * calculated using distanceKm, year in departureDate, and cabinClass. If there is a future flight
330+ * requested in this calendar year, we do not support Tier 1 emissions and will fallback to Tier 2
331+ * or 3 emissions. If the requested future flight is in not in this calendar year, we will return
332+ * an empty response. We recommend that for future flights, computeFlightEmissions API is used
333+ * instead. If there are no estimates available for a certain flight with any of the three
334+ * methods, the response will return a Scope3FlightEmissions object with empty emission fields.
335+ * The request will still be considered successful. Generally, missing emissions estimates occur
336+ * when the flight is unknown to the server (e.g. no specific flight exists, or typical flight
337+ * emissions are not available for the requested pair). The request will fail with an
338+ * `INVALID_ARGUMENT` error if: * The request contains more than 1,000 flight legs. * The input
339+ * flight leg is missing one or more identifiers. For example, missing origin/destination without
340+ * a valid distance for TIM_EMISSIONS or TYPICAL_FLIGHT_EMISSIONS type matching, or missing
341+ * distance for a DISTANCE_BASED_EMISSIONS type matching (if you want to fallback to distance-
342+ * based emissions or want a distance-based emissions estimate, you need to specify a distance). *
343+ * The flight date is before 2019 (Scope 3 data is only available for 2019 and after). * The
344+ * flight distance is 0 or lower. * Missing cabin class. Because the request is processed with
339345 * fallback logic, it is possible that misconfigured requests return valid emissions estimates
340346 * using fallback methods. For example, if a request has the wrong flight number but specifies the
341347 * origin and destination, the request will still succeed, but the returned emissions will be
0 commit comments