#xandert.93
pastel wave
unborn girder
Can you share the evt_xxx IDs please
latent anvil
ok
"id": "evt_1M8rfsLdDSIKKHr7wtgN4DQl"
"id": "evt_1M8rftLdDSIKKHr7D8lr05nY"
"id": "evt_1M8rftLdDSIKKHr7fCeNJ1Zv"
But word of warning, this seems to be happening every time I update any product's price
unborn girder
Thanks. I guess this is just a byproduct of how the Dashboard operates when updating these objects. Is there a particular concern you have?
latent anvil
Is this not the case if I update a price using the API?
ocean ice
I imagine it's the same , the dashboard is just calling the API under the hood
latent anvil
Okay
So isn't this a bug?
Surely there's no need for product.updated to be called twice?
ocean ice
not sure what you mean, I see two separate API calls, and each one lead to a separate product.updated event
latent anvil
What are the two calls?
In the dashboard, I just update the product price and then hit save
And personally, in my mind, this should only result in the price.updated event firing. Like I also said, none of the product's attributes (aside from updated) change either, so I don't understand why product.updated fires twice too
ocean ice
if you look at each event they have a Source link which is a link to an API request
latent anvil
I can't seem to find it looking at the event object
Nonetheless, do you happen to know why product.updated fires twice when a price is updated?
ocean ice
I don't happen to know no
latent anvil
I can't seem to find it looking at the event object
I've found it and am inspecting
latent anvil
I don't happen to know no
Is it not implausible that it's a bug?
Just that I don't want to my own database to update twice because product.updated is firing twice, when I believe it should only fire once.
ocean ice
not sure what I can say really
ocean ice
latent anvil
Overall, I'm not even sure why product.updated fires, since none of it's attributes change. I could understand if the reference to the Price object changed, for instance, but it doesn't