How to ensure the serialization of Directory sync webhook event?

[inker-kuo]

I checked directory sync web hook payload send from OKTA "user.updated" event looks like

{
  "header": {
    "accept": "application/json, text/plain, */*",
    "content-type": "application/json",
    "boxyhq-signature": "t=1739515853824,s=xxxx",
    "user-agent": "...",
    "content-length": "864",
    "accept-encoding": "gzip, compress, deflate, br",
    "host": "...",
    "connection": "keep-alive"
  },
  "body": {
    "event": "user.updated",
    "tenant": "...",
    "product": "...",
    "directory_id": "...",
    "data": {
      "id": "...",
      "first_name": "...",
      "last_name": "...",
      "email": "...",
      "active": true,
      "raw": {
        "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
        "userName": "...",
        "name": {
          "givenName": "...",
          "familyName": "...",
          "middleName": "...",
          "honorificPrefix": "...",
          "honorificSuffix": "..."
        },
        "emails": [
          { "primary": true, "value": "...", "type": "work" }
        ],
        "displayName": "...",
        "locale": "en-US",
        "externalId": "...",
        "active": true,
        "id": "...",
        "title": "...",
        "nickName": "...",
        "phoneNumbers": [
          { "primary": true, "value": "012345678910", "type": "work" }
        ],
        "groups": []
      }
    }
  }
}

Can I assume the sync events for a single connection will delivered in ordered with a single web hook handler setup?
Or I can count on the t=timestamp field in boxyhq-signature field for sort out the event order?

[deepakprabhakara]

@inker-kuo We'll get back to you on this shortly.

[deepakprabhakara]

@inker-kuo To ensure order you will need to enable https://boxyhq.com/docs/jackson/deploy/env-variables#dsync_webhook_batch_cron_interval which will then ensure the events are queued and sent as received. Without this the ordering cannot be fully guaranteed and is best effort.