Webhook with id object.id=null

API and Webhooks
1

Just received meeting.participant_left with id: null :crying_cat_face:

  "event": "meeting.participant_left",
  "payload": {
    "account_id": "SKrPQMSSS9yHCN4yBQgZZg",
    "object": {
      "duration": 0,
      "start_time": null,
      "timezone": null,
      "topic": null,
      "id": null,
      "type": 0,
      "uuid": "Csxibxe7QFuunH3ZvHuPLg==",
      "participant": {
        "leave_time": "2020-03-21T18:08:38Z",
        "id": "_VvMCStBSDO1y0ZfugOH5g",
        "user_id": "16778240",
        "user_name": "XXXXX@gmail.com"
      },
      "host_id": ""
    }
  }
}
2

Hey @alon,

Is this issue one off, or are you seeing this for all your webhooks?

Thanks,
Tommy

3

this is a one off issue. Only happened once up until now.

1 Like
4

Hey @alon,

Can you please let us know if it happens again?

Thanks,
Tommy

5

this still keeps happening - two events with id: nil

{
  "event": "meeting.participant_joined",
  "payload": {
    "account_id": "NDB67sTER76OfLRdu54ojw",
    "object": {
      "duration": 0,
      "start_time": nil,
      "timezone": nil,
      "topic": nil,
      "id": nil,
      "type": 0,
      "uuid": "bnZzerojS+GwI0tcajGMfQ==",
      "participant": {
        "id": "",
        "user_id": "0",
        "user_name": "EXTRACTED",
        "join_time": "2020-03-17T09:45:12Z"
      },
      "host_id": ""
    }
  },
  "webhook": {
    "event": "meeting.participant_joined",
    "payload": {
      "account_id": "NDB67sTER76OfLRdu54ojw",
      "object": {
        "duration": 0,
        "start_time": nil,
        "timezone": nil,
        "topic": nil,
        "id": nil,
        "type": 0,
        "uuid": "bnZzerojS+GwI0tcajGMfQ==",
        "participant": {
          "id": "",
          "user_id": "0",
          "user_name": "EXTRACTED",
          "join_time": "2020-03-17T09:45:12Z"
        },
        "host_id": ""
      }
    }
  }
{
  "event": "meeting.participant_joined",
  "payload": {
    "account_id": "NDB67sTER76OfLRdu54ojw",
    "object": {
      "duration": 0,
      "start_time": nil,
      "timezone": nil,
      "topic": nil,
      "id": nil,
      "type": 0,
      "uuid": "k9PUNwOyTlmvDkMN6xJcLA==",
      "participant": {
        "id": "_a75uU0cQliAeb2lgi_JNw",
        "user_id": "16778240",
        "user_name": "EXTRACTED",
        "join_time": "2020-03-16T18:54:30Z"
      },
      "host_id": ""
    }
  },
  "webhook": {
    "event": "meeting.participant_joined",
    "payload": {
      "account_id": "NDB67sTER76OfLRdu54ojw",
      "object": {
        "duration": 0,
        "start_time": nil,
        "timezone": nil,
        "topic": nil,
        "id": nil,
        "type": 0,
        "uuid": "k9PUNwOyTlmvDkMN6xJcLA==",
        "participant": {
          "id": "_a75uU0cQliAeb2lgi_JNw",
          "user_id": "16778240",
          "user_name": "EXTRACTED",
          "join_time": "2020-03-16T18:54:30Z"
        },
        "host_id": ""
      }
    }
  }
6

Iā€™m guessing this is an issue of some job worker communicating with a replication DB which is not synced yet, hence it does not find the meeting object.
Is it reasonable to think that if I fail the webhook with 500, the next retry will contain the meeting id? Or is the retry mechanism separated and the same event JSON will be sent anyways?

7

this is acutally happening quite a lot

8

Hey @alon,

We will look into this issue. (ZOOM-147866)

Unfortunately the retry logic has been temporarily turned off, details here:

Thanks,
Tommy

9

Hey @alon,

We have identified the issue and are working on a fix.

Thanks,
Tommy

1 Like
10

it seems like this bug still exists.
Just received an event of participant_left with id null

{
  "payload": {
    "account_id": "****",
    "object": {
      "uuid": "FguRDZM7SjuNIi1cEqYDvw==",
      "participant": {
        "leave_time": "2020-06-25T15:03:16Z",
        "user_id": "****",
        "user_name": "****",
        "id": "rE-N_v64Tw2u0LeNzxKKjA"
      },
      "id": null,
      "type": 0,
      "topic": null,
      "host_id": "",
      "duration": 0,
      "start_time": null,
      "timezone": null
    }
  },
  "event": "meeting.participant_left"
}
11

Hey @alon,

We are looking into this.

Apologies for the inconvenience.

Thanks,
Tommy