You're viewing **Apigee Edge** documentation. [Go to the **Apigee X** documentation](http://cloud.google.com/apigee/docs). info On Tuesday, October 7, 2014, we released a new cloud version of Apigee Edge. > [!NOTE] > **Note:** If you have questions, contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support). > > 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 are fixed in this release. | Topic | Description | |---|---| | No soapAction header in SOAP API proxies MGMT-1112 | When a WSDL included a soapAction with no value, an API proxy generated from that WSDL did not include a soapAction header, which caused an error. The soapAction header is now generated for such API proxies. | | Slow retrieval of developers and apps in UI MGMT-1060 | In the Edge management UI, retrieval of large numbers of developers and developer apps was slow. This issue has been fixed. | | Developer Apps list limit MGMT-1059 | The Developer Apps page on the Edge management UI can now show all records that are present in the backend instead of the earlier limitation of 10,000 apps. | | API import permissions MGMT-1006 | Edge management UI administrators who had access to only specific APIs were not able to import new revisions to those APIs. This issue has been fixed. | | InvalidateCache policy deployment errors MGMT-845 | Deployment errors were being thrown on new InvalidateCache policies because of the auto-populated `default`, a setting which duplicated previously deployed policies. This issue has been fixed by creating an empty CacheResource element. | | Logout when exporting Developers from the UI AXAPP-1178 | On the Developers page in the management UI, using the Export feature triggered an immediate logout from the UI. This issue has been fixed. | | Inaccurate analytics reports AXAPP-1133 | Inaccuracies were occurring in Edge Analytics reports. This issue has been fixed. |