Release Notes > Known issues

Known issues

This topic describes the known issues for Administrator. Not all monthly releases include known issues.

October 2025 known issues

Issue	Description
CBDM-39196	When you create a serverless runtime environment using AWS PrivateLink for service network endpoints in Administrator, the external ID property is incorrectly marked as required and shows an error if you leave it empty. Workaround: Add a value for the external ID property and save the environment even if you don’t use the external ID.
CBDM-39144	When a mapping runs successfully in a serverless runtime environment using AWS PrivateLink for service network endpoints, the job status might fail to update in Informatica Intelligent Cloud Services.
CBDM-39076	When you create an advanced cluster in the Jakarta region, the cluster can’t use Spot Instances. The cluster runs with only On-Demand Instances.
POP-75490	When you use the cluster uninstaller to clean up resources for an elastic runtime environment and your organization uses a secrets manager, it takes an hour for the process to complete and for the changes to appear in the user interface.
POP-74854	When you edit a user role that has accents or Norwegian characters in the name, you can’t save the changes.
POP-74849	When you rename a user role on the User Roles page, you can save the role even if the new name includes the following invalid characters: #?`\|{}"^&[]/\ Workaround: Select the role on the User Roles page, and then rename the role on the user role details page.
POP-74447	Users with only Read permissions on a Secure Agent group can change the list of services or connectors for the runtime environment through the REST API or the user interface.

April 2025 known issues

Issue	Description
POP-68905	In the user settings, the user interface incorrectly allows you to configure summary email settings for Critical Notifications even though Informatica doesn't send summary emails for these notifications.

February 2025 known issues

Issue	Description
POP-65000	If you log in using OAuth and you include a commit tag when you check in an object to an Azure DevOps repository, the check-in action fails. Workaround: Log in using a personal access token that permits use of commit tags.