--- schema_version: "1" id: 532b7ffffda9cbd74b04f22501d6785eb416673ae9871ff7b5b5dff93664a87b title: Known Issues and Limitations for MuleSoft Composer for Salesforce collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/composer-salesforce/ms_composer_release_notes_ki.md canonical_url: https://docs.mulesoft.com/composer-salesforce/ms_composer_release_notes_ki source_site: docs.mulesoft.com content_type: documentation content_hash: ce2e707c7d6a6181018180e4eeb89589afa77130a2c8b2841536ce2f062d432b description: MuleSoft Documentation Site latest: true --- --- product: Composer for Salesforce --- # Known Issues and Limitations for MuleSoft Composer for Salesforce > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The following list displays known issues and limitations for MuleSoft Composer for Salesforce. The list is sorted by the date in which the known issue or limitation appeared. ## September 12, 2025 ### Composer Platform
Known IssueWorkaroundID

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

## August 19, 2024 ### Salesforce
Known IssueWorkaroundID

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

## May 7, 2024 ### NetSuite
Known IssueWorkaroundID

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

## October 31, 2023 ### Composer Platform
Known IssueWorkaroundID

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

## May 31, 2023 ### SAP S/4HANA Cloud
Known IssueWorkaroundID

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

## March 22, 2023 ### Google BigQuery
Known IssueID

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

W-12696210

## August 3, 2022 ### RPA
Known IssueWorkaroundID

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.

Complete the following steps:

  1. Delete the step in the flow.

  2. Re-add the step in the flow.

  3. Refresh the process list.

  4. Select the new process.

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

## July 13, 2022 ### Composer Platform
Known IssueWorkaroundID

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.

## April 29, 2022 ### Workday
Known IssueWorkaroundID

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)

## April 28, 2022 ### HTTP
Known IssueWorkaroundID

After changing the text in the Example Request field, the HTTP Request fields do not clear.

Rebuild the action.

W-11052290

Some API endpoints expect a list as input. Composer only supports creating one list from another.

Add a previous step that returns a list to your flow and use it as a basis for the list required in the HTTP request.

When testing a connection, the Request Body field appears even if the Request Method field is set to GET.

None

## January 5, 2022 ### NetSuite
Known IssueWorkaroundID

An error occurs in Composer when testing your flow.

In your Chrome browser, click Developer Tools and then click Network. In the Network tab in Chrome, test your flow again. If you encounter the INSUFFICIENT PERMISSIONS error, complete the following steps:

  1. In NetSuite, access your role configuration.

  2. Click Permissions and then click Setup.

  3. Ensure that the following permissions are set to Full:

    • Control SuiteScript and Workflow Triggers in Web Service Request

    • SOAP Web Service

    • User Access Tokens

    • Custom Body Fields

    • Custom Column Fields

    • Custom Entity

    • Custom Item Fields

    • Custom Item Number Fields

    • Custom Lists

    • Custom Record Types

    • Custom Transaction Fields

  4. Reestablish the NetSuite connection. If the error continues to appear, contact Support.

None

## July 1, 2021 ### Jira
Known IssueWorkaroundID

The following standard fields are not supported at this time:

  • Affects version

  • Fix version

  • Environment

  • Component

None

None

Custom fields containing the following list components fail to render:

  • Text field (multi-line)

  • Labels

  • Checkboxes

  • Radio Buttons

  • Select list (multiple-choice)

  • Select list (cascading)

None

None

In the Status field, the In Progress value sometimes appears twice.

None

None

After creating a case in Jira, the Update issue action does not update the value in the Reporter field. Additionally, the value in this field must be blank for the Update issue action to succeed.

To update the value in the Reporter field, you can manually update the case record in Jira.

None

Custom fields fail to appear.

Reset your Jira connection by deleting the connection and re-authenticating your Jira account.

None

When you create an issue, you may encounter a 400 error in the output metadata.

Disregard this error.

None

## June 2, 2021 ### Composer Platform
Known IssueWorkaroundID

The Already editing somewhere? dialog appears, but you aren’t editing the flow in another tab.

Log out of Composer and log back in to resume work.

CAPO-47

When using the fromDateToTime or the fromStringToDateTime function in the Custom Expression Editor, the value returned is off by one day. For example, if you enter 04/27/2022 T00:00:00Z, the value returned is 4/26/2022 5:00:00 PM.

## May 19, 2021 ### Slack
Known IssueWorkaroundID

If you select the Create Message action in Slack, only public channels appear.

None

CCONN-765

## April 13, 2021 ### NetSuite
Known IssueWorkaroundID

If a NetSuite data pill is used in a Slack message that also contains text, testing fails for the NetSuite to Slack flows.

None.

CPLAT-1288

If a user has not completed any field mappings in the NetSuite Update Record action, then testing will not start.

None.

CPLAT-1292

## March 15, 2021 ### Composer Platform
Known IssueWorkaroundID

If you don’t see the New Flow button on the Recently Viewed list page, switch to the All page.

None.

CAPP-1625

If you see a blank area instead of the Home page contents when you first log in to Composer, clear your browser cookies and reload.

None.

CAPP-2051

You can’t access the Add Connection button from a trigger or action once it has been created.

To change a connection to a new connection of the same system type:

  1. Add an action to the end of your flow, which displays the Add Connection button.

  2. Create your new connection.

  3. Delete the action you added.

  4. In the trigger or action where you want to change to the new connection, click the change icon (three dots).

  5. Click Change Connection. The new connection is listed.

After you create a trigger, you can’t delete that step.

If you want to change the data source, for example switching from Salesforce to Workday, create a new flow.

If you want to change the instance of the same data source, but the connection for that source doesn’t exist yet:

  1. Add an action to the end of your flow. In the action, create the connection you need.

  2. Delete the action.

  3. Open the trigger and use Change Connection to change to the new connection.

CAPP-1550

As part of the Salesforce action Get records, you can’t query based on a Date field.

None.

CPLAT-1126

### Google Sheets
Known IssueWorkaroundID

A space in the name of your Google Sheet worksheet can cause an error during testing.

Remove the space and rerun the test.

CCONN-735

### Salesforce
Known IssueWorkaroundID

Composer doesn’t set the value of some required Boolean fields on the User object. You must set these values in the relevant step.

None

CAPP-2009

### Tableau
Known IssueWorkaroundID

Only one flow can append to the same Tableau data source. If more than one flow or app outside of Composer accesses the data source at the approximate same time, a Composer error occurs.

None

CCONN-714