Salesforce Pub/Sub Connector Release Notes

The grpc library is upgraded to version 1.76.0 to address reported security vulnerabilities.

W-20139044

The connector now supports graceful shutdown of gRPC connections, allowing active requests to complete before the service terminates to prevent data loss or connection errors during restarts.

W-20139044

The connector now correctly throws the ConnectionException error to Mule runtime if JWT token generation fails. Previously, the connector logged the error but incorrectly reported a successful reconnection, which prevented the reconnection strategy from triggering and stopped event processing.

W-20727817

The connector now includes the Inactivity Watchdog Scheduler to address issues where the subscriber intermittently stops receiving platform events without logging errors. Use the new Inactivity Watchdog Scheduler Frequency and Inactivity Watchdog Scheduler Time Unit fields to enable this scheduler.

W-20347755

The connector now auto-generates x-client-trace-id during the publish API call, and you can view this ID in the logs.

W-19643054

The connector now correctly obtains a new session when receiving the Invalid Session ID found in SessionHeader: Illegal Session. Session not found exception.

W-18048086

Session IDs are now logged at the DEBUG or TRACE level instead of the INFO level by default.

W-19251792

The com.fasterxml.jackson.core:jackson-core dependency is upgraded to version 2.18.3 to address reported security vulnerabilities.

W-18355862

The io.grpc dependency is upgraded to version 1.66.0 to address reported security vulnerabilities.

W-18355862

The org.apache.santuario:xmlsec dependency is upgraded to version 2.2.6 to address reported security vulnerabilities.

W-18355862

The com.fasterxml.jackson.core:jackson-databind dependency is upgraded to version 2.18.3 to address reported security vulnerabilities.

W-18355862

The org.apache.commons:commons-compress dependency is upgraded to version 1.27.1 to address reported security vulnerabilities.

W-18355862

The com.google.guava:guava dependency is upgraded to version 33.4.8-jre to address reported security vulnerabilities.

W-18355862

The Avro dependency is upgraded to version 1.11.4 to address a reported security vulnerability.

W-17819091

The EventDTO class, which is the response for the Subscribe channel listener source, is moved from the internal package to the api package for easier access.

W-16393438

The connector now properly supports SSL/TLS when setting up the truststore configuration in the connection configuration.

W-15395279

The Bouncy Castle library (bcprov-jdk15on) is removed to address reported security vulnerabilities.

W-15301880

The connector now contains a fixed read timeout period if the connection is validated after the static IP feature is applied in CloudHub 1.0.

W-15028700

The output metadata for the Subscribe Channel Listener source now uses lowercase fields that match the payload.

W-14608371

When the saved replay ID is encoded as a byte array in Object Store, the connector now correctly decodes the replay ID.

W-14108089

When there are connectivity issues with the connector, the replay ID is now correctly treated as valid, rather than the connector defaulting to the EARLIEST replay option.

W-13704839

When the connector is subscribed to multiple channels using the same configuration for all listeners, the listeners no longer fail to reconnect when the daily limit is reached.

W-13716068

The connector now properly reads the replay ID from the Object Store when using the Replay id from object store replay option in Subscribe Channel Listener.

W-13732644

The proxy configuration now works properly when connecting to the gRPC API.

W-12650923

The connector now handles numeric values properly when publishing events.

W-12704176

The connector now returns the EventId and CorrelationKey fields for all the events.

W-11743090

The connector no longer has metadata issues for CDC events.

W-11797082

The connector got stuck when specifying a value over 100 for the Batch events size field. Now, when specifying a value over 100, the connector prints a log message that the Batch events size field accepts a maximum value of 100, as per the Salesforce Pub/Sub API.

W-11637670

Consuming events no longer fails with an InvalidArgument error when using Replay id from object store as the Replay Option.

W-11554123

Consuming events no longer fails with a NumberFormat Exception when using Earliest as the Replay Option.

W-11450684

Consuming events no longer fails with an InvalidArgument error when using Custom replay id as the Replay Option and providing a number in the replay ID or when using Replay id from object store as the Replay Option.

W-11450737