What values are used for retryableErrors

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

I’m having an issue setting the retries for the SnowFlake connector following the documentation.

What values are supposed to be valid for retryableErrors.

This is what I am trying to set. Thanks!

[
{
“op”: “replace”,
“path”: “/connectorAttributes/conSnowflakeApiRetrySleepTimeSeconds”,
“value”: 60000
},
{
“op”: “replace”,
“path”: “/connectorAttributes/conSnowflakeApiRetryMaxAttempts”,
“value”: 3
},
{
“op”: “add”,
“path”: “/connectorAttributes/retryableErrors”,
“value”: [
“InvalidConfigurationException”,
“RuntimeException”
]
}
]

2

Hi @chris_mort,

In the body of the POST request, you can enter retryable errors as follows:

"retryableErrors": [
 "Unauthorised 401",
 "Http 1.1/",
 "InvalidConfigurationException",
 "RuntimeException”
],

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.

Thanks!

3

Thanks Dinish, Do these belong in the path of /connectorAttributes?

4

If i add that to the body of the update source partial API, it get teh following error

{
“detailCode”: “400.1 Bad request content”,
“trackingId”: “670ac62bdc1f445caa24248281d5e941”,
“messages”: [
{
“locale”: “en-US”,
“localeOrigin”: “DEFAULT”,
“text”: “The request was syntactically correct but its content is semantically invalid.”
},
{
“locale”: “und”,
“localeOrigin”: “REQUEST”,
“text”: “The request was syntactically correct but its content is semantically invalid.”
}
],
“causes”:
}

5

@chris_mort . Yes, it is inside connector attributes of the source config json.
Below is an example:

“connectorAttributes”: {
“retryableErrors”: [
“connection timeout”
]
}