Release Notes for MuleSoft Composer for Salesforce - 2026

Use MuleSoft Composer for Salesforce to build connected experiences faster. You don’t need to wait for development resources to unlock data, integrate apps, and automate business processes that create real customer value.

New versions are automatically available once they are released; you don’t need to perform any tasks to move to the new version.

See Known Issues and Limitations for MuleSoft Composer for Salesforce for a list of known issues and limitations by date.

May 28, 2026

Fixed Issues

Issue Resolution	ID
To prevent excessive errors from abandoned processes and reduce the risk of service incidents, MuleSoft Composer automatically deactivates flows that experience continuous failures and alerts affected users. Deactivation occurs only when a flow meets both of these conditions: 100 or more consecutive errors 10 or more days of continuous failure You can reactivate a deactivated flow at any time.	W-22571502

Issue Resolution

To prevent excessive errors from abandoned processes and reduce the risk of service incidents, MuleSoft Composer automatically deactivates flows that experience continuous failures and alerts affected users. Deactivation occurs only when a flow meets both of these conditions:

100 or more consecutive errors
10 or more days of continuous failure

You can reactivate a deactivated flow at any time.

W-22571502

March 19, 2026

Fixed Issues

Issue Resolution	ID
Jira Connector now correctly updates the watermark for the triggers, and captures all subsequent new and updated issues.	W-20186115
In Jira Connector, all triggers now correctly update the watermark when multiple records share the same minute-level timestamp. The connector now uses cursor-based pagination to retrieve all records for a specific watermark before updating the watermark value. This prevents duplicate record retrieval and resolves issues where flows enter an indefinite waiting state.	W-21090825

Issue Resolution

Jira Connector now correctly updates the watermark for the triggers, and captures all subsequent new and updated issues.

W-20186115

In Jira Connector, all triggers now correctly update the watermark when multiple records share the same minute-level timestamp. The connector now uses cursor-based pagination to retrieve all records for a specific watermark before updating the watermark value. This prevents duplicate record retrieval and resolves issues where flows enter an indefinite waiting state.

W-21090825