Currently we are using the Salesforce component version 2.23.4.
Every 3 hours the component needs to resubscribe due to expiring token (expected behavior). Sometimes however it fails on:
It turns out (not in the logging) that the server returns additional information:
As described in the Salesforce documentation here: https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/streaming_handling_errors.htm
the 503 Server too busy is a documented error that should/can be retried.
It would greatly add to the resilience of our system if the Salesforce component would automatically retry a subscribe if failed due to a temporary error. The same backoff mechanism as for the reconnect could apply.
Currently our workaround is to detect a 403 (more information is not available, like the failureReason) and restart the whole Camel subsystem.