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

On Tuesday, June 20, 2017, we began releasing a new version of Apigee Edge for Public
Cloud.

> [!NOTE]
> **Note:** **Private Cloud customers** : Is this cloud release included in your Private Cloud version? See your version's release notes to see which cloud releases it contains. Also, see [About release
> numbering](https://docs.apigee.com/release/apigee-edge-release-process) to understand how you can figure it out by comparing release numbers.
>
> **Questions or issues?** Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support)
>
> **Release notifications** : See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications).
>
> [Release notes home page](https://docs.apigee.com/release/notes/apigee-release-notes)

## New features and updates

Following are the new features and updates in this release.

### Custom consumer key and
secret naming rules

Naming rules and validation have been updated for [creating a custom consumer key and secret for a developer app](https://docs.apigee.com/management/apis/post/organizations/%7Borg_name%7D/developers/%7Bdeveloper_email_or_id%7D/apps/%7Bapp_name%7D/keys/create). Consumer keys and secrets can
contain letters, numbers, underscores, and hyphens. No other special characters are allowed.

The custom key/secret creation process is more fully documented in [Import existing consumer
keys and secrets](https://docs.apigee.com/api-platform/publish/import-existing-consumer-keys-and-secrets). (MGMT-3916)

## Bugs fixed

The following bugs are fixed in this release. This list is primarily for users checking to see
if their support tickets have been fixed. It's not designed to provide detailed information for
all users.

| Issue ID | Description |
|---|---|
| MGMT-4059 | > [!WARNING] > **Warning:** **MGMT API return 500 for GET DebugData** > The [Get debug session transaction data](https://docs.apigee.com/management/apis/get/organizations/%7Borg_name%7D/environments/%7Benv_name%7D/apis/%7Bapi_name%7D/revisions/%7Brevision_number%7D/debugsessions/%7Bsession_name%7D/data/%7Btransaction_id%7D) management API was throwing an HTTP 500 status code on errors. The API now throws a 404s instead. > If you have scripts that are catching a 500 status code when getting transaction > data, update those scripts to look for 404s. |
| MGMT-3517 | **Incorrect proxy revision in proxy deployment error message** |