Troubleshoot integration

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info

Here are some common issues and their troubleshooting steps for the Apigee Edge API hub connector integration.

API metadata does not show up in API Hub

Initial sync time: It can take a few hours for the initial synchronization to start and for API data to appear in API Hub. It is recommended to wait for few hours.
Plugin instance status:
- Verify that the plugin instance in API Hub has not been deleted or changed.
- Ensure the correct instance Resource Name is configured in your Apigee Edge API Hub connector settings.

Proxy deployed but information in API Hub is not accurate

Propagation delay: Allow a few minutes for deployed proxy information to propagate and be reflected in API Hub.

User opt-in via settings API fails

Permissions: Ensure the user attempting the POST request to enable API Hub connector has orgadmin permissions for the Apigee Edge organization.
Payload format: Double-check the JSON payload for the POST request to ensure it is correctly formatted and includes the valid gatewayId.

User org stopped syncing without changing anything in Edge

Plugin instance status (API Hub side):
- Verify if the associated plugin instance in API Hub has been deprovisioned, deleted, or altered. Any changes on the API Hub side can directly impact synchronization from Edge.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-09-18 UTC.