You are here:
MuleSoft for Flow: Integration Limits & Considerations
When establishing connections to external systems, keep these limitations in mind.
Required Editions
| View supported editions. |
| This feature requires the MuleSoft for Flow: Integration add-on. Professional Edition requires the API access add-on. To purchase, contact your Salesforce account executive. |
| MuleSoft for Flow: Integration features used with Agentforce require the Foundations or Agentforce 1 edition. To purchase these editions, contact your Salesforce account executive. |
General Limitations
- MuleSoft for Flow: Integration supports only in auto-layout, not freeform.
- You can’t use Transform View for the output of an External System Change-Triggered flow directly. Select a field from the $Event output in Inline View and then switch to Transform View to use that data as source data.
- Transform View supports the global constants
TrueorFalsefor Boolean literal values. Select the constant from the available options. Don’t enter it manually.
Reaching Per-Transaction Flow Limits
If your flow includes multiple actions and has been failing because it’s hitting
per-transaction flow
limits, insert a Wait
for Amount of Time element before the action in your flow. By setting
the wait time to 1 minute, the system can process the changes before
continuing, which helps manage resource usage and makes sure that the workflow runs
smoothly.
Testing External System Change-Triggered Flows and Flows by Using Third-Party Connectors
The maximum number of records a test returns is 5 when testing an External System Change-Triggered flow or a flow that uses a third-party connector.
Missed Triggers in Polling-Based Flow Automations
When polling a flow, sometimes flow automations can miss triggers.
The flow creates a Sales Order in an external system when the status of an Opportunity changes to Closed Won in Salesforce.
-
The flow polls every 5 minutes.
-
At 1:00:00 PM, the system marks multiple opportunities as Closed Won. The flow polls at 1:00:00 PM and returns records that match the criteria and have a
lastModifiedDateTimevalue greater than 12:55:00 PM. Salesforce returns 5 opportunities.Flow fetches these 5 opportunities and runs 5 flow interviews to process in the external system.
-
The interviews timestamp is 1:00:00 PM, and the flow polls again at 1:05:00 PM. At 1:05:00 PM, the flow polls for records that match the criteria and have a
lastModifiedDateTimevalue greater than 1:00:00 PM.
Salesforce processes data in the background. There’s a likelihood that an Opportunity closed at 1:00:00 PM was committed to the database at 1:00:05 PM with a 1:00:00 PM timestamp. If a record updates and results in a delay, it's possible that the trigger doesn't run.
Agentforce Features: Dynamic Actions Limitations
Agentforce features in MuleSoft for Flow: Integration don’t support dynamic actions in third-party connectors. A flow can’t use Agentforce if it relies on dynamic metadata from these connectors: NetSuite, Salesforce, and Zendesk.
Limits & Considerations in Third-Party Connectors
Connecting to an External System with Named Credentials
To customize you connection security and manage API performance, you can use your own OAuth application - via named credential with external credentials - with all supported connectors.
Here are general limitations in third-party connectors.
- The maximum number of returned records is 10,000 for the Get <Records> actions.
- The name of an external service can’t exactly match the name of a third-party connector. Use a unique name for an external service to avoid naming conflicts and issues in your flows.
Here are specific limits & considerations in third-party connectors.
- HubSpot Connector
- If you attempt to associate a Salesforce Opportunity with a HubSpot Deal, the association fails.
- NetSuite Connector
- Triggers and Get Records actions only support text-compatible custom fields. However, use the Get Record action to return all custom fields for a record, regardless of its data type.
- When flows with NetSuite connections use MuleSoft for Flow: Integration Query Builder and trigger automatically, the system doesn’t return line items and lists. To return line items or lists, use the Get Record action with the relevant record type.
- These fields aren't supported on the NetSuite Customer object:
taxItem, taxSchedule,
projectTemplate, and projectTemplateId.
The underlying NetSuite REST API doesn't expose these fields for creating or updating Customer records. There’s currently no direct workaround in the connector. Instead, use one of these alternative methods:
- Use custom fields and NetSuite automation to handle the data.
- Update the fields manually in the NetSuite UI.
- Contact NetSuite customer support to request that these fields be prioritized for their REST API.
- Microsoft Dynamics 365 Business Central Connector
- When creating a Sales Invoice or Sales Order, enter a valid Customer Number.
However, the Customer API doesn't require that all mandatory fields include values
(such as Gen. Bus. Posting Group, Customer Posting Group, and Tax Area Code).
Therefore, creating a Customer record through the API or a flow without these values
is possible. If you use that Customer record to create a Sales Invoice or Sales Order,
the operation fails with the
Error: Customer Posting Group must have a value in Customer.error message. To ensure successful creation of Sales Invoices and Sales Orders, verify that the Customer Posting Group field populates for each customer record.
- When creating a Sales Invoice or Sales Order, enter a valid Customer Number.
However, the Customer API doesn't require that all mandatory fields include values
(such as Gen. Bus. Posting Group, Customer Posting Group, and Tax Area Code).
Therefore, creating a Customer record through the API or a flow without these values
is possible. If you use that Customer record to create a Sales Invoice or Sales Order,
the operation fails with the
- Salesforce Connector
- If you authenticate a Salesforce to Salesforce connection during authentication, the
OAUTH_APPROVAL_ERROR_GENERICerror sometimes appears because the security policy for Connected Apps requires explicit approval for those Connected Apps that created before the policy rollout. To resolve this issue, the destination organization's admin must explicitly approve the Connected Apps by completing the steps:- For the initial configuration, the Salesforce admin requires the Approve Uninstalled Connected Apps permission.
- For established orgs, the Salesforce admin approves the Salesforce Connector Connected App.
After one Salesforce admin approves the app, subsequent users can authenticate without needing the Approve Uninstalled Connected Apps permission.
- After an API user successfully authenticates a connection but then runs a connection
test, the test sometimes fails with the error
Connection test failed: The resource doesn't exist. This failure occurs because, during the test, the connector attempts to run a query against the Describe endpoint of the Account sObject. This endpoint request fails if the API user has insufficient permissions. To establish and test the connection, the user creating the connection requires these permissions, which are via a Profile or permission set:- API Enabled
- Read access to the Account sObject
- If you authenticate a Salesforce to Salesforce connection during authentication, the
