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

On Monday, August 20, 2018, we began releasing a new version of Apigee Edge for Public Cloud.
**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-notes/content/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/content/apigee-release-notes)

## New Features and Updates


Following are the new features and updates in this release.

| Issue ID | Component Name | Description |
|---|---|---|
| 110996654 | Management Server | **Add API to GET and SYNC distributed flow hook deployment status** |

## 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 | Component Name | Description |
|---|---|---|
| 113904969 | Management Server | **Issue with deletion of API proxies in demo orgs** Fixed September 10, 2018. |
| 112192639 | Management Server | **Management server tries to deploy to router even if deployment to message processor failed** |
| 112133192 | Connectors | **Extensions: JSON validation on \<Input\> element is too strict to inject flow variables** <br /> In an [ExtensionCallout policy](https://docs.apigee.com/api-platform/reference/policies/extension-callout-policy), if the [**\<Input\>**](https://docs.apigee.com/api-platform/reference/policies/extension-callout-policy#input_element) element contains a JSON payload, you can include Edge message flow variables using the standard curly braces syntax (for example, `{client.ip}`) without getting an invalid JSON error. |
| 111503565 | Management Server | **"mdc" property returned on get environment management API calls** |
| 110719914 | Management Server | **Create Sense built-in roles for existing and new orgs** |
| 78105568 | Management Server | **Shared flow deployments do not show up in /org/{org}/sharedflows/{sharedflow}/deployments management API calls after updating a deployed shared flow** |