We collected about 1.5 days worth of Webhooks back in October 2022 from a client.
Certain Webhook Types had missing "createdTime" keys under their "data".
This appeared to happen with about 1/2 of the "task:ended" and all of the "task:on-hold" Webhooks. We are able to fix some of the Webhook "createdTime" values by using a matching Webhook "id" from a "agent:state_change" Webhook. If we cannot find a matching Webhook "id" with a valid "createdTime", we have to rely on the current Unix timestamp of our webserver that the Webhooks are being sent to, which is not ideal as we have seen differences of a few seconds due to travel time and the fact each server's time clocks are not synced.
Do you mean the "taskId"? I don't see a interactionID key in the in any of the Webhooks we received. One "taskId" sample that has both "task:ended" and "task:on-hold" Webhooks with missing "createdTime" keys is "49036f7b-ceed-410e-8581-32eda14c1cf5".
Thanks, BlakeR, Yes, the taskID, I believe this taskID '49036f7b-ceed-410e-8581-32eda14c1cf5' is from October and we store logs only for the last 30days, Do you have a more recent example, if so, please do share the taskID.
Unfortunately, we do not have any recent taskIDs to share. In the next month or so, we should be working with another client. I'll reply to this thread with examples from those taskIDs if the issue is still present.