PO Update (closed) webhook notification being sent more than once?

GraphQL API
24

Hi @Luisperrone
Yes sure, here they are:

purchase_order
id:1929393
po_number:PO 52
po_id:52
po_uuid:UHVyY2hhc2VPcmRlcjoxOTI5Mzkz
account_id:69683
line_items
0
id:91402cf63239b896b0f3
quantity:1
quantity_received:0
sku:TEST1SKU
status:closed
webhook_type:PO Update
25

Hi @Raj

There are two webhooks in our logs, each corresponding to the respective endpoints registered.
One is for n8, and the other is for make.

If you think this is still an issue, please send everything you received from the webhook.

Have a nice day!

27

Hi @Luisperrone , Deja vu…

image
image786×524 18.4 KB

28

There are no dupes for that PO for the same endpoint.

Can you provide all the info from both exports so i can look into it?

29

Actually I don’t even have access to the data from the other endpoint, so ALL the exports I’ve given you so far are ONLY from the n8n endpoint.

30

For PO 52, I see there were at least seven changes created within minutes regarding the status, from pending to close.
Apart from the test you are doing, do you have an example of a real PO having this issue?

31

I can’t close a client PO for my testing, and I can’t enable client PO notifications till the duplicate notifications stop for good - this is why I have been testing on dummy POs.
I’ll enable notifications on client POs and target them all to me for a day.

33

I reviewed all the PO updates on the last day and found a duplicate.
I escalated to engineering already and’ll let you know as soon as i have an update.

Have a nice day!

1 Like
34

Yes! Was it the PO with legacy_id 2284360?
I got duplicate notification on this one (since I rerouted all real PO close notifications to myself).
Funny thing is, around the same time I got a PO close notification also for another PO (legacy_id 2295235), and this one was not a duplicate!

Thank you so much for your help investigating this

35

It was PO_ID 2223818. It looks like we are not sending the webhook fast enough, so a second one is generated.
I’ll let you know of any other updates.

Have a nice day!

1 Like
36

@Luisperrone
Adding this here in case the info helps finding the problem - I just received the FOURTH notification for the same PO close.
PO: PO 2
Legacy_id: 2280876
SKU: 42674490638370

(This isn’t a test PO)

37

@Raj

I’ll check that one, too, and update the engineering ticket.
Keep bringing examples as you see them, as it helps set the priority for the team.

Have a nice day!

1 Like
38

Hi @Luisperrone
So, I have a couple updates

  • For a few POs, I only received a single notification, though nothing new there since that happens side-by-side with the duplicates all the time.
  • The main update is that for the PO ‘X 8.30 DELIVERY’ (legacy_id 2304480), I received a record fourteen notifications! I looked at the notification timings and they seemed to be in batches of 3+3+3+3+2.
  • I also looked at the history of above PO in dashboard, and here are the last few entries (not sure what the date change action is or if that’s causing the duplicates, but might be useful in investigating)
    image
    image761×261 10.5 KB
39

Hi @Raj

The engineering team is working on this, and I have passed this last example on to them.
An engineer is assigned to a ticket that might potentially fix this issue.
I’ll keep you updated.

Have a nice day!

1 Like