In developing a web services application using the Web Services Connector, we’re hitting a situation where the target application occasionally returns a HTTP/502 error even though it still has valid data to send, and if we retried the request, we’d likely get back valid data.
I understand that other connectors support “retryable errors” – does the Web Services Connector support retryable errors?
Yes, the Web Services connector does support specifying retryableErrors.
However I think one thing to keep in mind is that specifying the list of retryableErrors in an Application definition is a way to control the ProvisioningResult in a ProvisioningPlan after a provisioning attempt being set to retry instead of failed. The “Provision with retries” subprocess workflow will inspect the ProvisioningPlan and attempt to retry provisioning items marked as retry.
That is to say for any application, the retryableErrors are only germane to provisioning (or writing) to the application and are not applicable to aggregation (reading).
Thank you! Bad news for me, since I need this for aggregation, but appreciate the quick and complete answer.