Deployments to CloudHub 1.0 from within Anypoint Code Builder run on vCores allocated to the root organization only. You cannot deploy to a business group even if it has a sufficient vCore allocation. If your root organization lacks a sufficient vCore allocation, the error Failed to deploy to CloudHub: 400 occurs.
-
Workaround:
Use Runtime Manager to deploy to the business group in the Sandbox environment in CloudHub, or increase the vCore allocation to the root organization in the Sandbox environment. To reallocate resources to your root organization, see Redistribute Resources Between Existing Business Groups. To manage environments, see Environments. For additional help, contact your organization administrator for Anypoint Platform.
|
W-13974860 |
When the desktop IDE launches for the first time, a corrupted dependency (.m2\repository\net\minidev\accessors-smart\1.2\accessors-smart-1.2.pom ) can block the Anypoint Code Builder - Integration Extension when extracting the Mule runtime operation.
|
W-14047707 |
When launching the cloud IDE for the first time from Anypoint Code Builder, you must allow popups.
|
None |
The link to the help page code-server Editing evolved dialogue does not work.
|
W-13488500 |
The list of trusted authors for a directory or file is not persistent across different browsers.
|
W-12408476 |
The UI does not provide a notification after you change the region in settings.json .
|
W-13184670 |
Selecting a project folder from the PROJECTS view in the Explorer causes Anypoint Code Builder to produce the error The file is not displayed in the text editor because it is a directory.
|
W-13143061 |
Adding a space at the end of an API specification name causes an error.
|
W-13115894 |
In dark mode, error messages are difficult to read because of an issue with the color scheme in API Console.
|
W-11351113 |
API Console does not reflect changes immediately.
|
W-12564212 |
The RAML editor does not handle indentation correctly when you use tabs or spaces.
|
W-11625929 |
Anypoint Code Builder displays a Cannot read properties of undefined (reading 'name') error when failing to resolve a GraphQL type.
|
W-12482229 |
The Back button in the command palette does not work when running the MuleSoft: Import Asset from Exchange command.
|
W-12012889 |
The rescaffolding icon is not disabled after you rescaffold an API specification.
|
W-14048631 |
Moving the editors while searching for components from the UI canvas causes your search to be canceled.
|
W-13172200 |
The canvas UI does not displays flows and components after scaffolding a Mule application.
|
W-13162142 |
Using autocompletion to create a parameter for the value field in the XML adds an extra #[] statement.
|
W-12444650 |
Autocompletions and code suggestions do not follow the standard VSC/LSP pattern.
|
W-12564179 |
Autocompletion does not work properly when more than one connector has the same prefix.
|
W-10667510 |
Anypoint Connector for NetSuite (NetSuite Connector) does not have an icon in the component palette.
|
W-13173111 |
Anypoint Connector for Apache Kafka (Apache Kafka Connector) does not display the Test Connection option.
|
W-12553536
|
When you import a Mule project from Studio to Anypoint Code Builder, a DataWeave expression can produce syntax errors (identifiable by a red, wavy underline) in the configuration XML. The issue occurs because the IDE’s tooling is unable to automatically fetch the required dependencies from Mule runtime when the project loads.
|
W-14037343 |
If you import a Mule project into Anypoint Code Builder that points to Anypoint Exchange (Exchange) version 3, authentication and dependency resolution errors occur because Anypoint Code Builder currently supports Anypoint Exchange version 2 only.
|
W-14037012 |
DataSense doesn’t identify functions provided by a connector.
|
W-12448776 |
DataSense doesn’t reflect array structures at the payload’s root level.
|
W-12263085 |
DataSense doesn’t work when a tag spans multiple lines.
|
W-12482310 |
DataWeave doesn’t recognize the larger context to which samples belong. So DataWeave requests sample data for all scripts within a single component.
|
None |
DataWeave validations to produce Invalid input errors on some multiline scripts because Anypoint Code Builder does not decode Unicode characters for new lines in XML ( ). This limitation does not interrupt the correct execution of your Mule application.
|
W-11750473 |
Code highlighting breaks when you define a DataWeave multiline expression. This limitation does not interrupt the correct execution of your Mule application.
|
W-11492623 |
Anypoint Code Builder displays a popup message about opened ports when creating a Mule project.
|
W-12482078 |
Ending a second thread in a Scatter-Gather component before the first thread finishes freezes processing in Anypoint Code Builder.
|
W-10601367 |
Updates to metadata in one component don’t trigger metadata validation in subsequent components. This issue causes Anypoint Code Builder to display potential issues in the subsequent components.
|
W-12215165 |
The Mule configuration XML file sometimes fails to open immediately after you create a new Mule project.
|
W-10601832 |
The Batch Job processor is not supported.
|
None |