Unexpected delivery updates two days after delivery completed

Bug Reporting
1

Hey there,

We recently observed some very odd webhooks in our production environment concerning job ID 284482450 / delivery ID 293243285 / client reference 320841. All timestamps in UTC.

We made our job creation request at 2024-04-28T14:26:51.3533003Z, and received the standard lifecycle of webhooks. The last expected webhook (delivery update / delivered) arrived at 2024-04-28T15:09:08.5123105Z:

{"event":"delivery","type":"update","data":{"id":293243285,"trackingUrl":"https://stuart.followmy.delivery/293243285/4e0bc3b4ef8c32779193fa01a9483662","clientReference":"320841","driver":{"status":"on_duty","latitude":51.61057406,"longitude":-0.2526614,"name":"[redacted]","firstname":"Bhavishaben","lastname":"[redacted]","phone":"+447466152676","picture_path_imgix":null,"transportType":{"code":"e_bike"}},"status":"delivered","transportType":{"code":"e_bike"},"packageType":{"code":"medium"},"etaToDestination":"2024-04-28T17:08:30.000+02:00","etaToOrigin":"2024-04-28T17:04:00.000+02:00","cancellation":{"canceledBy":"operations","reasonKey":"other","comment":null}}}

This is all as expected. But then things get weird.

About two days later, we received 5 additional delivery update webhooks with the same delivery ID and client reference as above:

  1. Received 2024-04-30T07:10:22.1256112Z:
{"event":"delivery","type":"update","data":{"id":293243285,"trackingUrl":"https://stuart.followmy.delivery/293243285/4e0bc3b4ef8c32779193fa01a9483662","clientReference":"320841","driver":{"status":"busy","latitude":51.61183,"longitude":-0.27564,"name":"[redacted]","firstname":"Grace","lastname":"[redacted]","phone":"+441632960146","picture_path_imgix":null,"transportType":{"code":"motorbike"}},"status":"picking","transportType":{"code":"walk"},"packageType":{"code":"medium"},"etaToDestination":"2024-04-30T09:14:06+02:00","etaToOrigin":"2024-04-30T09:14:06+02:00","cancellation":{"canceledBy":null,"reasonKey":null,"comment":null}}}
  1. Received 2024-04-30T07:12:44.9137237Z:
{"event":"delivery","type":"update","data":{"id":293243285,"trackingUrl":"https://stuart.followmy.delivery/293243285/4e0bc3b4ef8c32779193fa01a9483662","clientReference":"320841","driver":{"status":"busy","latitude":51.61183,"longitude":-0.27564,"name":"[redacted]","firstname":"Frank","lastname":"[redacted]","phone":"+441632960146","picture_path_imgix":null,"transportType":{"code":"motorbike"}},"status":"picking","transportType":{"code":"walk"},"packageType":{"code":"medium"},"etaToDestination":"2024-04-30T09:20:29+02:00","etaToOrigin":"2024-04-30T09:16:29+02:00","cancellation":{"canceledBy":null,"reasonKey":null,"comment":null}}}
  1. Received 2024-04-30T07:16:41.2132733Z:
{"event":"delivery","type":"update","data":{"id":293243285,"trackingUrl":"https://stuart.followmy.delivery/293243285/4e0bc3b4ef8c32779193fa01a9483662","clientReference":"320841","driver":{"status":"busy","latitude":51.61183,"longitude":-0.27564,"name":"[redacted]","firstname":"Grace","lastname":"[redacted]","phone":"+441632960146","picture_path_imgix":null,"transportType":{"code":"motorbike"}},"status":"picking","transportType":{"code":"walk"},"packageType":{"code":"medium"},"etaToDestination":"2024-04-30T09:24:25+02:00","etaToOrigin":"2024-04-30T09:20:25+02:00","cancellation":{"canceledBy":null,"reasonKey":null,"comment":null}}}
  1. Received 2024-04-30T07:21:26.1492203Z:
{"event":"delivery","type":"update","data":{"id":293243285,"trackingUrl":"https://stuart.followmy.delivery/293243285/4e0bc3b4ef8c32779193fa01a9483662","clientReference":"320841","driver":null,"status":"pending","transportType":{"code":"walk"},"packageType":{"code":"medium"},"etaToDestination":null,"etaToOrigin":null,"cancellation":{"canceledBy":"operations","reasonKey":"courier_issue","comment":null}}}
  1. Received 2024-04-30T07:38:45.6986089Z:
{"event":"delivery","type":"update","data":{"id":293243285,"trackingUrl":"https://stuart.followmy.delivery/293243285/4e0bc3b4ef8c32779193fa01a9483662","clientReference":"320841","driver":{"status":"busy","latitude":51.61183,"longitude":-0.27564,"name":"[redacted]","firstname":"Charlie","lastname":"[redacted]","phone":"+441632960146","picture_path_imgix":null,"transportType":{"code":"motorbike"}},"status":"picking","transportType":{"code":"walk"},"packageType":{"code":"medium"},"etaToDestination":"2024-04-30T09:46:30+02:00","etaToOrigin":"2024-04-30T09:42:30+02:00","cancellation":{"canceledBy":null,"reasonKey":null,"comment":null}}}

We’re not quite sure what to make of these five “delayed” webhooks. They don’t seem to bear any relation to the actual real-world job itself.

Notably, these unexpected webhooks put our system in a bad state, so we’re trying to better understand what happened here. Thoughts?

Thanks in advance,
Mirek

2

Hi @mirek,

Thank you for reporting this.

I also see the last delivery update webhook was sent at 28/04/2024, 16:09:08.

I will be interested in understanding how you consume our webhooks and working with you to resolve this issue.

I will send a private message to discuss this in more detail.

3

Hi there, just following up here. Any idea as to why those delayed (and seemingly unrelated to the job) webhooks were sent?