You're viewing Apigee Edge documentation.
View Apigee X documentation.
On the following dates, we began releasing component updates to Apigee Edge for Public Cloud:
- Management Server: March 30, 2023
- Message Processor: June 12, 2022
- Router: May 10, 2022
- Management Server: April 28, 2022
Help & notifications
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 to understand how you can figure it out by comparing release numbers.
Questions or issues? Get help here.
Release notifications: Go to http://status.apigee.com and click Subscribe to Updates.
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|
Latency was improved for app creation when multiple API products are included in the payload.
Improved deployment time for a proxy bundle with a large OAS resource file.
Use the correct allowed duration for the freemium rate plan in Apigee Monetization.
An issue was fixed to ensure that the freemium duration is respected by Apigee Monetization. With this fix, app developers can use the rate plan for free during the configured duration. Before this fix, the duration was being calculated incorrectly on the backend. See Configure a freemium plan.
The SwaggerParser library upgrade throws stricter validation errors during proxy deployment for the OASValidation policy.
An issue was fixed where turning on Apigee debug caused the runtime to skip some asynchronously executed policies.
An issue was fixed where in the GenerateJWT policy, when specifying
When a forward proxy was used between the Message Processor and Target server, inconsistent target details were captured in analytics. Target details in analytics were sometimes of the actual target and sometimes of the proxy. This issue was fixed so target details captured in analytics are always those of the actual target.
An issue was fixed in the DecodeJWT policy where when declaring
Improved resilience and logging of DNS management code in message processors.
An issue was fixed where the VerifyJWT policy did not allow the
An issue was fixed where requests to the Python callout in a shared flow
failed due to
OAS validation errors now throw HTTP 400 status; previously, 500 status was thrown.
Miscellaneous Security updates and fixes.
An issue was fixed where a failure to connect to a Syslog server could cause the MP to restart.
attempted to modify the variable
An issue was fixed where the DeleteOAuthV2Info policy was failing to remove the access token.
An issue was fixed where a message processor would sometimes boot up successfully even though it was not able to load all underlying repositories.
An issue was fixed where permissions containing both a wildcard (
A proxy revision was returning an HTTP 400 status error when used as a
The Message Processor will now reuse existing target IPs once if DNS resolution fails during DNS cache refresh.
The flow variable
An issue was fixed where the AccessControl policy reported errors when
An issue was fixed where JWS policy threw a