Retry Configurations
Provisioning Retries
Note
For more information on SailPoint's REST APIs, refer to Best Practices: REST API Authentication and REST API - Update Source (Partial) in the SailPoint Developer Community.
SailPoint connectors that support provisioning operations have the ability to retry a failed operation based on configurable error messages.
The retryableErrors
entry in the connector configuration is a list of strings that the connector searches for in the error message received from the managed
Add a list of retryable error messages to the attributes map of the
For example,
Use the Identity Security Cloud API by sending a PATCH request to the /v3/sources/{id} endpoint:
PATCH https://{orgName}.api.identitynow.com/v3/sources/:id
In the body of the PATCH, enter the retryable errors as follows:
[
{
"op": "add",
"path": "/connectorAttributes/retryableErrors",
"value": [
"<error_message_1>",
"<error_message_2>"
]
}
]
Note
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.
Maximum Retry Count
The maxRetryCount
parameter enables you to configure the maximum number of attempts the connector retries a failing operation before terminating it.

Sets the maximum number of attempts before terminating a failing operation.
Integer
Default: 2
Set the parameter as follows using the REST API:
PATCH https://{orgName}.api.identitynow.com/v3/sources/:id
In the body of the PATCH, enter the maximum retry count as follows:
[
{
"op": "add",
"path": "/connectorAttributes/maxRetryCount",
"value": <required_value>
}
]
Note
For more information on SailPoint's REST APIs, refer to Best Practices: REST API Authentication and REST API - Update Source (Partial) in the SailPoint Developer Community.