API Proxy timeouts on new Apigee tenancy

We have just had a new Apigee Business tenancy setup and have lifted our existing proxes, shared flows and KVMs from another tenancy as they are all being deployed via CI/CD using apigeetool so it was straightforward.

We are getting random timeout issues when regression testing the endpoints that we never saw on the other tenancy.

Is there some rate limiting on API calls or some way we can diagnose why when a frontend api calls a backend one using a service callout. The request never turns up on the backend api proxy and on the frontend it eventually timesout on the call.

Is there any way to debug / diagnose the front end router and see the nginx logs to make sure the service callout is being sent?

0 2 141
2 REPLIES 2

Is this Private or Public Cloud?

If it's private, I'd expect to see any service callout failures in the message processor logs, but you won't have access to those on public cloud and would need to raise a case.

There is no outbound rate limiting on service callouts.

This is the public cloud Apigee tenancy.

We will need to raise a case and see what is happening as there doesn't seem to be any way to debug why these requests are disappearing.