Checking for configuration synchronization issues

Updated: April 15, 2026

Want to summarize with AI?

Verify configuration synchronization status in Cisco Application Centric Infrastructure by checking for pending transactions that may affect system performance.

Check for configuration synchronization issues to identify delays in transactions involving user-configurable objects and use the information for debugging purposes.

When you make a request in Cisco Application Centric Infrastructure (APIC)—for example, changing a configuration—you generally see immediately that the change has occurred. However, if you encounter an issue with Cisco APIC, you can check in the GUI to see if there are any transactions involving user-configurable objects that have yet to take effect. You can use information in the panel to help with debugging.

The Configuration Objects Pending Resolution panel in the Cisco APIC GUI tells you if there are delays.

Before you begin

Procedure

Log in to Cisco APIC.
Click the settings icon (the gear symbol) in the upper right of the screen and choose Config Sync Issues.
In the Configuration Objects Pending Resolution panel, check if anything is listed in the table.

If there are no entries in the table, there are no synchronization issues.
If there are any entries, capture the information in the table and use it for debugging or working with Cisco support.

You have successfully checked for configuration synchronization issues. If entries appear in the Configuration Objects Pending Resolution panel, you have identified pending transactions that require attention for troubleshooting purposes.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.