Account sync during aggregation process

We are seeing issue with custom SaaS Connector where before aggregation(std:account:list) finished, account sync (std:account:update) is initiated. Due to this nature of this source, often we do have large number of users requiring sync. Having all those calls happening at the same time causing rate limit violation on the source service.
Is there a way to prevent account sync until aggregation is done?

Hi Ralph,

You could potentially use the Update Attribute Sync Config API to modify the attribute sync. Before aggregation, call the API to turn off attribute sync on the appropriate fields:

{
  "source": {
    "type": "SOURCE",
    "id": "2c9180835d191a86015d28455b4b232a",
    "name": "HR Active Directory"
  },
  "attributes": [
    {
      "name": "email",
      "displayName": "Email",
      "enabled": false,
      "target": "mail"
    },
    {
      "name": "firstname",
      "displayName": "First Name",
      "enabled": false,
      "target": "givenName"
    }
  ]
}

Then once aggregation is complete, re-enable the attribute sync:

{
  "source": {
    "type": "SOURCE",
    "id": "2c9180835d191a86015d28455b4b232a",
    "name": "HR Active Directory"
  },
  "attributes": [
    {
      "name": "email",
      "displayName": "Email",
      "enabled": true,
      "target": "mail"
    },
    {
      "name": "firstname",
      "displayName": "First Name",
      "enabled": true,
      "target": "givenName"
    }
  ]
}

Thanks @philip-ellis for great idea!
Question: if I disable during aggregation and reenable it after, would account sync actually get triggered? I was under impression only aggregation event or identity attribute change event triggers account sync…

The way I went around this issue is by adding short random sleep at the beginning of account update. This way when we do have large number of accounts to sync they do not come in at the same time form service endpoint rate limits. This have solved our issue.

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