Release Notes > Known issues
  

Known issues

The tables in this section describe the known issues for Metadata Command Center. Not all monthly releases include known issues.

November 2025 known issues

Issue
Description
MDP-11430
When you perform connection assignment for Informatica Intelligent Cloud Services catalog sources that include mappings from Reference 360, the reference objects might remain unresolved. As a result, you might see reference objects in the lineage instead of resolved objects from the endpoint catalog source. This issue occurs when you assign connections to endpoint catalog sources that contain Reference 360 objects extracted prior to the November 2025 release.
CTP-412234
You can't use the browse metadata extraction filters feature on the Amazon Web Services (AWS) UK POD. This issue occurs because the CCICOREAgent custom license is not included in the Intelligent Data Management Cloud Edition in Administrator.
SCAN-25915
When you run a metadata extraction job on a Data Lake catalog source, the job returns incorrect results if a file and folder at the same hierarchy level share the same name. This issue also affects the hierarchy representation of assets on the Hierarchy tab on the results page in Data Governance and Catalog.
SCAN-27770
When you run an SAP Sales & Service Cloud metadata extraction job on services, the results include metadata from additional services not specified in the filters.
SCAN-28168
When you browse files and folders in the metadata extraction filters, the Select an object dialog box doesn't display files and folders in alphabetical order. This issue occurs when there are more than 100 files and folders in the source system.
SCAN-28283
You can clone a catalog source even if you don’t have Read permissions on the Secure Agent group. The cloned catalog source displays a blank Runtime Environment field on the Configuration tab.

April 2025 known issues

Issue
Description
CDGC-78610
When you run data quality jobs with rule occurences, the jobs skip rules that include invalid or missing output port mappings. However, the Monitor page in Metadata Command Center doesn't display the skipped rules in Skipped Rule Occurences and no debug logs are generated.