Webservice connector retry question

Identity Security Cloud (ISC) ISC Discussion and Questions
, , ,
1

We have tried to configure the retryable errors in the webservice connector as follows:

   "retryableErrors": \[

        "409",

        "Locked by: {hostname}"

    \],

This is the exact error we are receiving from the application:

[“Exception while updating account.Url: https:////Api/USERS_API?login\u003dRXS893, Message: 409 : {\“errorcount\”:1,\“log\”:[{\“Error\”:true,\“message\”:\”(Error) Application name: Apache-HttpClient/4.5.13 (Java/11.0.28)\\r\\nLocked by: {hostname}\\r\\nLocked on: 10/27/2025 3:34:02 PM\\r\“,\”

Does ISC have to match on the exact error string? Is there a way we can configure it to only match part of the string? Since the date/time is part of the error, we cannot match it exactly, so a substring match would be needed here.

2

Hi @jsr749,
We had the same case and were advised that it does not have to be an exact match, but that a substring should be sufficient.

Retry Configurations.

We did not end up going with the retryable errors for other reasons, but substrings of the error messages are the recommended input for this.

Though these are technically not required, we were also advised that if you set the Retryable Errors, you should also set the below attributes (with example values, adjust as you need). RetryWaitTime is wait in minutes.

"maxRetryCount": 10,
"retryWaitTime": 90,

This article helped us a lot when we dove into it:

How to Configure Retries for Connector Aggregations and Provisioning Actions - Identity Security Cloud (ISC) / ISC Community Knowledge Base - SailPoint Developer Community

Good luck!

3

Thanks. But I don’t see where it says we can use substrings. This is from the web services connector manual: Error messages containing very specific information about date/time, sequence ID and so on must be avoided. Error codes or error message substrings would be good candidates for inclusion.

4

Actually, this seems to answer my question :grinning_face:

1 Like