Also, my apps turn webhooks on and off, ALOT - otherwise how do you prevent getting another webhook response when you just updated a product? For every product update, I have to deal with another webhook response coming into my system.
And there you have it. That is the real underlying issue. Not the fact that the activity log displays... activity logs... as it should, but that your app is spamming the activity log by unsubscribing from and subscribing to webhook events as a means of avoiding self-recursive updates. And yes, users should feel uneasy if their activity log goes bananas - that's one of the points of having one!
Yes, your app will have to deal with the 'oh yeah we just did this' whether you choose to check for updated_at (very fragile approach) or sleep your webhook handler for a bit and for a particular product ID (a tad less fragile, can work but scales like a ****) or actually maintain an ephemeral state correlating webhook events to requests dispatched from the handler to match the follow up event (your terminal case).
So we may agree to disagree if need be 😉
