When using the Replay Channel Listener of Salesforce Connector, the following warning message is observed in the logs periodically:
[2022-02-02 10:56:00.544] WARN AuthFailureListener [HttpClient@7c1cdd18-165] [event: ]: Couldn't connect to Salesforce streaming server because a 403 error has been returned. Handling 403.
Arguments: {message={advice={interval=0, reconnect=handshake}, channel=/meta/connect, id=33678, error=403::Unknown client, successful=false}, error=403::Unknown client}.
The 'sfdc-stream' cookie managed by the Salesforce load balancer has expired and it has a default 3 hour expiration. As a result, the CometD client (used by the Salesforce Connector) receives a "403::Unknown client" response from the Salesforce server. To continue consuming events Salesforce has clarified that 'if the client already subscribed, it is necessary to re-subscribe. If you need any further clarification from Salesforce you can contact them and refer to GUS ID W-7395361,W-19699543)
The error message you see is mentioned in the Salesforce error code and message information
These Warning/Error messages can be safely ignored if Salesforce Connector continues to subscribe to events after the Warning/Error messages are logged.
403::Unknown client messages. If event subscription is uninterrupted, no further action is typically required, as this behavior is often part of the CometD client's normal reconnection process.403::Unknown client messages are causing concern, are excessively verbose in logs, or if you suspect they are preventing proper event subscription, restart your Mule application. This action can clear the current state and force a fresh re-establishment of the CometD connection.Please refer to the documentation from Salesforce: Handling Streaming API 403 Errors
001119042

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.