Known Issues and Limitations for MuleSoft Composer

When you test a flow, Composer tracks a limited number of tracking notifications for each flow execution (100 by default) to show step-by-step results. When a flow generates more notifications, Composer drops the oldest ones. As a result, early steps can appear blank or not executed even though they ran and produced data.

Only the display is affected. Your flow logic runs, records are created, and the execution completes.

Composer isn’t designed for complex or large automations. The limitation depends on the complexity of the processing logic, not the size of the data. For example, a flow with 100 steps isn’t recommended. Complex flows can result in partial debug messages, slow load times, and other performance problems.

If early steps in a large flow appear blank after you test it, verify the results directly, for example, by checking the records created or updated in the target system.

Keep your flows smaller and more manageable. For use cases that require advanced or complex logic, consider Anypoint Code Builder.

W-24287812

Composer’s functionality may be subject to various limitations related to the external systems and their respective limits used in data retrieval. Composer is primarily intended for processing simpler and more lightweight datasets. It is important to understand that there is no single, rigid limit and that specific thresholds vary depending on each individual use case. For example, the following limits apply to Salesforce Connector.

For use cases requiring greater control, advanced logic, or larger datasets, users should consider Anypoint Code Builder.

W-19176552

In Salesforce Connector, the SALESFORCE:CONNECTIVITY Failed to get next element error is sometimes thrown when processing the next element of the loop.

Rerun the flow to catch the missed events. For more information, refer to the known issue.

W-16418279

When selecting a record type, if there is a large amount of metadata, the metadata resolver cannot parse the data within the three-minute time limit required by Composer and the Netsuite: Retrieving metadata for the step failed error sometimes occurs.

For more information, see the knowledge article.

W-15586159

When testing an Invocable Flow, if the value in the output fields was generated by a custom expression or if the value is either a List<Object> or a List<Primitive> data type, then the flow’s final output step does not display the test output data. Output fields that refer to data pills or variables display test output as expected.

None

None

When adding an action or a trigger, the Service field dropdown menu might appear empty, which prevents completing the connector configuration.

Similarly, during configuration, the Retrieving metadata for the step failed error might occur.

This is an intermittent issue that should resolve after a brief period of time.

W-13527982

Input parameter values of String or date data types must be provided between single quotes using the expression editor.

None

W-12696210

If connecting to a different RPA than one for which that the existing flow was built, the current RPA process is not automatically mapped to the processes in the new org.

None

When getting a JSON from RPA, you can pass a list of objects to a connector supporting lists. For example, you can pass the list of order line items to NetSuite.

None

None

When getting a JSON from RPA, you cannot use primitive values of a list when iterating the list. For example, a list of strings can be iterated, but you cannot do anything with the resulting values.

None

None

When deleting a connection, Composer ensures that there are no flows using that connection. If there are flows using that connection, they appear in a list in the Delete Connection window. However, in rare cases, flows created or edited before July 12, 2022 might not appear in the list.

In the Invoice object, all fields containing the data type number for amounts are sent as strings.

Using the Custom Expression Editor, you can use the typecasting function, fromStringToNumber, to change the field type from string to number. For example:

Unit Cost=fromStringToNumber(Sales Price)