Retry mechanism for synchronize attribute

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

If due to intermittent failure at the target system identity attribute does not gets synchronized with account attribute. When the connection establishes, synchronize attribute does not retry for synchronization on its own and we have to synchronize attribute manually. Is it a valid case or something can be done on this?

2

Hi @Amrit1897,

The attribute synchronization will be retried during the next account aggregation of the source or during the scheduled 8PM refresh, whichever is earlier.

2 Likes
3

Aware, but it should retry once error is resolved on target system.
But is not and on attribute sync manually it synchronizes the attribute.

4

Hi @Amrit1897,

I don’t think IDN has the capability to check the source status and re-trigger the failed provisioning tasks.

If the initial provisioning fails, IDN would do multiple retries in a short interval of time regardless of the source status.

This is what the document says regarding the retryable errors.

image
image1058Ă—245 26.6 KB

5

And you have an option to add retryable errors in the source config as well, if that helps your case.

“retryableErrors”: [
“Unknown Host”,
“Service Unavailable”
],
6

Hey @Amrit1897 , hope you’re good.

On the sources that support Retry, you’ll have a field called : retryableErrors

"retryableErrors": [
            "Server is not operational",
            "Connect to APP gateway failed"
        ],

you can try to add this field in your source and add other error messages and se if it works.

Best!

7

Hi Ivan,

How do you add this, when i enter that into the body of the source partial update partial I get this error.

{
    "detailCode": "400.1 Bad request content",
    "trackingId": "b66c126715844875bcc1e007267ebb96",
    "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": []
}
8

hey @chris, glad to hear back from you!

I’ve tried using the Yannick vscode plugin and it worked. If you don’t have it you can use the patch operation.

I think the path would be :
/connectorAttributes/retryableErrors
and the value would be a list with the existing values plus the one you need to add.

best!

9

How can we test this, once I make changes in the source?
Will IDN run some background task, or I have to run anything?

10

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.