You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

On Wednesday, August 09, 2023, we released a new version of Apigee Edge for Public Cloud.

If you have questions, go to [Apigee Customer Support](https://www.googlecloudcommunity.com/gc/Apigee/bd-p/cloud-apigee).

For a list of all Apigee Edge release notes, see [Apigee Release Notes](https://docs.apigee.com/release/notes/apigee-release-notes).

## Bugs fixed

The following bugs and changes included in this release.

| Topic | Description |
|---|---|
| Change to time range | Previously, the synchronous query time range of 6 months was not enforced. It will be enforced now. |
| Change to latency percentile algorithm | Previously, the latency percentile algorithm used the [`CUME_DIST`](https://cloud.google.com/bigquery/docs/reference/standard-sql/numbering_functions#cume_dist) method to calculate the exact percentile. With this release, the algorithm uses the [`APPROX_QUANTILES`](https://cloud.google.com/bigquery/docs/reference/standard-sql/approximate_aggregate_functions#approx_quantiles) method to optimize the memory usage. |
| `topk` bug fixed | The `topk` parameter lets you return the top k results when querying Analytics statistics. See [Sorting results by relative ranking](https://docs.apigee.com/api-platform/analytics/use-analytics-api-measure-api-program-performance#sortingresultsbyrelativeranking) for an example. Previously, a bug in the `topk` parameter caused a query to return k + 1 results for a given value of k. This has been fixed: queries with `topk=k` now return k results. |
| `tzo` bug fixed | The [`tzo`](https://apidocs.apigee.com/docs/stats/1/routes/organizations/%7Borg_name%7D/environments/%7Benv_name%7D/stats/%7Bdimension_name%7D/get) parameter lets you offset the time zone when querying Analytics statistics. Previously, a bug in the `tzo` parameter caused the time zone offset to be twice what it should have been. For example, `tzo=240` caused the offset to be 480. This has been fixed: `tzo` now creates the correct offset. |