Apigee known issues

This page applies to Apigee and Apigee hybrid.

View Apigee Edge documentation.

Select one or more of the following to filter this page:

This section lists known issues for Apigee components. For a list of bugs, new features, and other release information, see the release notes.

Issue ID Affects Status Description


hybrid 1.11.0 OPEN Cert validation failures may return a 502 instead of a 503 error response when users add the tag <Enforce>true</Enforce> in the target <SSLInfo> block for default validation of TLS target endpoint certificates.


Apigee OPEN OASValidation policy does not work with global security requirements in OpenAPI specifications

If the OASValidation policy specifies an <OASResource> with security requirements set at a global level, the security requirements are not enforced.

Workaround: To ensure enforcement, all security requirements must be set at the operation level in the OpenAPI specification passed in the <OASResource> element of the OASValidation policy.


hybrid 1.10.2
hybrid 1.10.3
FIXED in Apigee 1-10-0-apigee-6 and
Hybrid 1.10.3-hotfix.1
Apigee hybrid does not validate the target certificate by default.

See About setting TLS options in a target endpoint or target server.


hybrid 1.10.0 and later FIXED in hybrid 1.10.3 Installing Apigee hybrid 1.10 on OpenShift (OSE) can fail with out-of-memory errors.

Installing or upgrading to Apigee hybrid 1.10.0 through 1.10.2 could fail on OSE due to out-of-memory issues. Fixed in Apigee hybrid version 1.10.3.


hybrid 1.10.1 OPEN apigee-udca may not honor the http proxy settings.

If the firewall forces all traffic through a forward-proxy, apigee-udca may go into a crash-loop backoff state.


hybrid 1.8.0 and later
OPEN OASValidation policy fails with Unable to parse JSON error.
  • The OASValidation Policy fails when the JSON content does not match the anticipated pattern. For example, if a header is expecting a value in the format <text>@<text> and is populated with text missing the @ symbol, the policy will fail with an Unable to parse JSON error.
  • If the OASValidation policy specifies an <OASResource> containing a path parameter that utilizes a $ref schema, the policy will fail with an Unable to parse JSON - Unrecognized token error.

    Workaround: Do not use $ref in the path parameters of the OpenAPI spec specified in the <OASResource> element.


hybrid 1.8.0 and later
OPEN Deployment Issues with OAS Validation while using circular reference.
  • Apigee deployment will fail for OAS Validation policy when using circular references for OpenAPI 3.0.0 specification as it gets into an infinite loop.
  • Workaround: Use an OpenAPI specification yaml without circular references.


Apigee 1-10-0-apigee-3
hybrid 1.8.8
hybrid 1.9.3
FIXED in Apigee 1-10-0-apigee-5
OPEN in hybrid
Proxy deployments that include the OASValidation policy may fail.

Proxy deployments that include the OASValidation policy may fail if:

  • The OpenAPI specification used for validation in the OASValidation policy is in YAML format, and
  • The YAML-formatted OpenAPI specification contains a floating number. For example:
    type: number
    example: 2.345


Apigee 1-10-0-apigee-1
FIXED Increase in latency for Message Logging policy when used with Cloud Logging.

To avoid increasing latency in responses to the client, the Message Logging policy should be attached to the PostClientFlow. For more information on using policies in PostClientFlows, see Controlling API proxies with flows.


hybrid 1.8.0 and later
hybrid 1.9.0 and later
OPEN Special characters not allowed in Cassandra Jolokia password

Use only alphanumeric characters for the Cassandra Jolokia password. Using special characters (including but not limited to "!", "@", "#", "$", "%", "^", "&", & "*") can cause Cassandra startup to fail.


Apigee OPEN Avoid concurrent API proxy or SharedFlow deployments

Concurrent deployment requests for a SharedFlow or API proxy can result in an inconsistent state in the Management Server where multiple revisions are shown as deployed. This can happen, for example, when concurrent runs of a CI/CD deployment pipeline occur using different revisions. To avoid this problem, avoid deploying API proxies or SharedFlows before the current deployment is complete.


hybrid 1.9.0 and later OPEN cert-manager pods on OpenShift version 4.7 to 4.10 do not start as expected

With cert-manager v1.10.1 on OpenShift versions 4.7 to 4.10, the cert-manager pods do not start as expected. To resolve the problem, modify the security config constraint as described in the cert-manager 1.10 release notes.


hybrid 1.9.0 and later FIXED Apigee Ingress gateway supports TLS1.2+ protocol/ciphers only

Apigee Ingress gateway only supports TLS1.2+, and not earlier versions of TLS.


hybrid 1.7.0 and later OPEN apigeectl getOrg does not follow HTTP_PROXY settings in overrides.yaml

Apigee organization validation does not follow HTTP Forward proxy rules set in overrides.yaml. Set validateOrg: false to skip this validation.


hybrid 1.7.0 and later
hybrid 1.8.0 and later
hybrid 1.9.0 and later
OPEN Web sockets not working with Anthos Service Mesh 1.15.3 in Apigee X and Apigee Hybrid

In certain circumstances, web sockets are not working for Apigee X and Apigee Hybrid when using Anthos Service Mesh 1.15.3-asm.6.


Apigee OPEN API product fails to load with a "no connections available" error

This error might be returned when attempting to load API products: "Products were not loaded successfully. Error: no connections available from the Apigee connect agent(s)."

The problem occurs after enabling VPC service control in the Google Cloud project and adding iamcredentials.googleapis.com as one of the restricted services in the service perimeter.

Workaround: Manually create an egress rule, such as the following:

    -serviceName: "iamcredentials.googleapis.com"
    identityType: ANY_IDENTITY


hybrid 1.7.0 and later
hybrid 1.8.0 and later
OPEN A race condition with encryption key lookup can cause KVM lookup failures.

In certain circumstances at very high throughput a race condition with encryption key lookup can cause KVM lookup failures.


hybrid 1.8.0 and later OPEN The default memory requests and limits for metrics pods have inadvertently changed in 1.8.x.

If you see problems with the apigee-telemetry-app or apigee-telemetry-proxy pods not running, change the metrics resources requests and resources limits properties to match the following defaults in Configuration property reference: metrics.

Configuration property Default value
metrics.aggregator.resources.requests.memory: 512Mi
metrics.aggregator.resources.limits.memory: 3Gi
metrics.app.resources.requests.memory: 512Mi
metrics.app.resources.limits.memory: 1Gi
metrics.appStackdriverExporter.resources.requests.memory: 512Mi
metrics.appStackdriverExporter.resources.limits.memory: 1Gi
metrics.proxy.resources.requests.memory: 512Mi
metrics.proxy.resources.limits.memory: 1Gi
metrics.proxyStackdriverExporter.resources.requests.memory: 512Mi
metrics.proxyStackdriverExporter.resources.limits.memory: 1Gi

Apply the changes with apigeectl apply with the ‑‑telemetry flag:

apigeectl apply --telemetry -f overrides.yaml


Apigee 1-9-0-apigee-16 OPEN API proxy and shared flow deployments taking up to 30 minutes.

API proxies and shared flows could take around 20 to 30 minutes to deploy in the runtime plane in certain circumstances due to a 'socket closed' error in synchronizer.


API hub FIXED New regions cause provisioning failure

Provisioning API hub using the UI fails if you select a region other than the following:

  • asia-east1
  • asia-southeast1
  • europe-west1
  • europe-west4
  • us-central1
  • us-east1
  • us-west1
  • us-west4


Documentation OPEN Apigee hybrid version selector

The Apigee hybrid version selector works only if you select or click directly on the text.


All OPEN The message "Precondition check failed" is displayed in the audit log.

This is expected to occur every minute and does not affect your billing cost.


hybrid 1.8.0 and later OPEN Socket bind error on the AKS platform

If installing hybrid on AKS, you may see this error:

envoy config listener '' failed to bind or apply socket options: cannot bind '': Permission denied

Workaround: Add the following svcAnnotations stanza to the overrides file:

service.beta.kubernetes.io/azure-load-balancer-internal: "true"

See Configure the hybrid runtime. See also Use an internal load balancer with AKS.


hybrid 1.8.0 and later OPEN MART sometimes unable to connect to FluentD.

When using Org-scoped UDCA, MART is sometimes unable to connect to FluentD. Org-scoped UDCA is the default in Apigee hybrid version 1.8. See orgScopedUDCA in the Configuration property reference.

N/A hybrid 1.6.0 and later OPEN apigee-logger not working on Anthos BareMetal with CentOS or RHEL.

After migration of apigee-logger from fluend to fluent-bit in Apigee hybrid version 1.6.6, the logger stopped working on Anthos BareMetal with CentOS or RHEL.


hybrid 1.5.0 and later OPEN Apigee Hybrid Dockerhub customers unable to pull images with Docker Content Trust enabled.

Users are encountering the following error when pulling images for Apigee Hybrid from Docker Hub: ERRO[0001] Metadata for targets expired. This applies to the following hybrid components:

  • google/apigee-authn-authz
  • google/apigee-mart-server
  • google/apigee-runtime
  • google/apigee-synchronizer


If you encounter this error, you can use one of the two following workarounds:

  • Switch to using gcr.io/apigee-release to pull hybrid images.
  • Disable docker content trust by setting the DOCKER_CONTENT_TRUST environment variable to 0
207762842 hybrid 1.5.0 and later OPEN Logs not shipped to Cloud Logging by apigee-logger.

Current apigee-logger configurations, including liveness probes, are incompatible with the Kubernetes runtime, resulting in logs not being shipped to Cloud Logging as expected. This problem also causes the apigee-logger pods to crash regularly. This issue affects Apigee hybrid installations on AKS, Anthos Bare Metal, and other platforms. Note that in some cases this issue results in excessive log volume.

203827738 Archive deployments OPEN Configurable API proxy without operations fails.

Proxies that do not contain operations, or contain operations without HTTP matches, will return a 404 error code if the request path does not contain exactly one segment in addition to the basepath. For example, requests to /basepath will fail, but requests to /basepath/user may succeed. To prevent failure, add an Operations section with at least one http_match to your configurable API proxy.

201429104 Apigee OPEN Wildcard in proxy basepath results in incorrect request path.

Usage of a wildcard (*) in the proxy basepath of a configurable API proxy results in forwarding incorrect request paths to the backend target.

To prevent incorrect request path forwarding, avoid using * in the configurable API proxy basepath until the issue is fixed.

191291501, 191000617 Apigee OPEN Changing the email address of a developer entity will fail in the UI.
191002224 hybrid 1.5.0 and later OPEN Changing an email address fails while using the PUT /organizations/{org_name}/developers/{developer_email} API.
184555974 hybrid 1.5.0 and later OPEN The apigee-logger Fluentd can't parse logs in the OpenShift cluster.
N/A Archive deployments OPEN Managing and debugging Apigee archive deployments in the UI is not supported

In the Apigee UI, you cannot view, confirm deployment status, or manage your archive deployments, as described Deploying an API proxy, or use the Debug UI as described in Using Debug. As a workaround, you can use gcloud or the API to List all archive deployments in an environment and use the Debug API.

N/A Archive deployments OPEN Rolling back an archive deployment is not supported

Rolling back an archive deployment is not currently supported. To remove a version of an archive deployment you need to either redeploy a previous version of an archive or delete the environment.

N/A Apigee in VS Code OPEN Google Authentication in policies is not supported in Apigee in Visual Studio Code (VS Code)

Google authentication in ServiceCallout and ExternalCallout policies, as described in Using Google Authentication, is not supported in Apigee in VS Code.

146222881 hybrid 1.3.0 and later OPEN Invalid HTTP Header error

Invalid HTTP Header error: The Istio ingress switches all incoming target responses to the HTTP2 protocol. Because the hybrid message processor only supports HTTP1, you may see the following error when an API proxy is called:

http2 error: Invalid HTTP header field was received: frame type: 1, stream: 1,

name: [:authority], value: [domain_name]

If you see this error, you can take either of the following actions to correct the problem:

  • Modify the target service to omit the Host header in the response.
  • Remove the Host header using the AssignMessage policy in your API proxy if necessary.

N/A Integrated portal OPEN SmartDocs
  • Apigee supports OpenAPI Specification 3.0 when you publish your APIs using SmartDocs on your portal, though a subset of features are not yet supported. For example, allOf properties for combining and extending schemas.

    If an unsupported feature is referenced in your OpenAPI Specification, in some cases the tools will ignore the feature but still render the API reference documentation. In other cases, an unsupported feature will cause errors that prevent the successful rendering of the API reference documentation. In either case, you will need to modify your OpenAPI Specification to avoid use of the unsupported feature until it is supported in a future release.

  • When using Try this API in the portal, the Accept header is set to application/json regardless of the value set for consumes in the OpenAPI Specification.
N/A Integrated portal OPEN Portal admin

  • Simultaneous portal updates (such as page, theme, CSS, or script edits) by multiple users is not supported at this time.
  • If you delete an API reference documentation page from the portal, there is no way to recreate it; you'll need to delete and re-add the API product, and regenerate the API reference documentation.
  • When customizing your portal theme, it may take up to 5 minutes for changes to fully apply.
N/A Integrated portal OPEN Portal features

Search will be integrated into the integrated portal in a future release.

N/A Integrated portal OPEN SAML identity provider

Single logout (SLO) with the SAML identity provider is not supported for custom domains. To enable a custom domain with a SAML identity provider, leave the Sign-out URL field blank when you configure SAML settings.

191815997 hybrid 1.6.0 and later OPEN If a hybrid customer configures a forward proxy for the API proxy, Google token will not work unless it has direct access to *.googleapis.com.
N/A Apigee OPEN API Monitoring and Cloud Monitoring show abnormal spikes

  • API Proxy request and response counts (for proxy and targets) show abnormal spikes

    Here is a sample showing such a spike:

    (view larger image)

  • Due to a bug, the system registers the count incorrectly for a brief period and the count is corrected. This happens where there is a reduction in API traffic (which results in a scale down of API gateways).
  • To distinguish actual spikes in requests vs. this issue, please consult the API Analytics page (specifically the Proxy Performance and Target Performance pages)

Affected Metrics:

  • apigee.googleapis.com/proxyv2/request_count
  • apigee.googleapis.com/proxyv2/response_count
  • apigee.googleapis.com/targetv2/request_count
  • apigee.googleapis.com/targetv2/response_count
203778087 hybrid 1.5.3 and later OPEN apigee-stackdriver-logging-agent currently runs as root.

Workaround: Disable the logging agent on hybrid.

205629443 Apigee OPEN If ServiceCallout is fire and forget (no <Response> tag), a race condition can occur if there is another policy that occurs after it.

Workaround: To maintain the fire and forget behavior:

  1. Add <Response>calloutResponse</Response> to the ServiceCallout.
  2. Set continueOnError to true.
207719377 Apigee FIXED in Apigee 1-11-0-apigee-1 If there is more than one SpikeArrest policy in a bundle, 502 errors will occur.

Workaround: Avoid using more than one SpikeArrest policy in the proxy to prevent the issue.

209097822 hybrid 1.5.0 and later
OPEN Dynamic updates to rate in spike arrest may not reflect immediately

For a particular key, if there is continuous traffic, the key may not be rate limited at the updated rate. If there is five minutes of no traffic for a particular key, the rate will be reflected.

Workaround: Redeploy the proxy with a new reference variable if the rate has to take effect immediately. Or use two conditional spike arrests with different flow variables to adjust the rate.

221305498 Apigee OPEN API Monitoring may display fault code of '(not set)'.

API Monitoring of Configurable API Proxies may display a fault code of '(not set)' for responses with a non-2xx status from the target.

246774745 Apigee OPEN Value of io.timeout.millis is not honored when used with multiple dynamic targets.

If a proxy sets two or more io.timeout.millis values in two or more flows using the same target host, only one io.timeout.millis value is honored.

245664917 hybrid 1.8.x OPEN Apigee hybrid upgrade error can be ignored

During upgrade to Apigee hybrid 1.8.x, after running apigeectl init and confirming that check-ready succeeded, you may notice, if you view the pods, that the Cassandra schema validation job is in an error state. This is a harmless condition, and you can safely move to the next step in the upgrade procedure.

300660653 Apigee OPEN An error should be, but is not, returned when deploying proxies with the same path to multiple environments that are attached to the same instance and environment group

Deploying proxies with the same path to multiple environments that are attached to the same instance and environment group is not allowed and should return a warning message about a base path conflict. Instead, no error is shown and the deployments appear to succeed.

Workaround: When deploying and after deployment, verify that there are not base path conflicts with deployed proxies and correct as needed.

301458133 Apigee OPEN Some proxy deployment attempts return an error that the revision is immutable

When attempting to save a previously deployed proxy, the deployment might fail with an error stating that the revision is immutable.

Workaround: Click the dropdown arrow next to the Save button and select Save as new revision. Then reattempt the deployment.

301845257 Apigee OPEN Attempting to deploy more than 800 proxies to an environment group fails with an error. The limit on which an error is returned is lower than 800 when the basepaths are longer than 15 characters.

N/A Apigee 1-9-0-apigee-23 OPEN TLS version upgrade required for clients experiencing Unsupported protocol errors

Updates to the default set of ciphers supported by Apigee servers to enhance security may result in Unsupported protocol errors for some TLS versions. Customers encountering these errors should review the full list of ciphers supported by the FIPS build of Envoy.

315874988 Apigee OPEN With gRPC proxy requests, gRPC trailers are removed from the response

When a call is made to a gRPC Target Server, the only trailer that's returned is the "grpc-status" trailer. All other trailers are removed from the response.