Could it be that you are triggering a publish event in the webhook target
I know this is an old post, but request loops are a problem for me too.
My webhook is only triggered by the Entry.publish event. When entries are published, my webhook saves some data from an external service into an entry field.
The webhook does this using a CMA PATCH request, which puts the entry into “changed” state. I need the entry to stay in “published” state.
Making a second CMA request to the /published endpoint creates an endless loop, like the one described in this post.
Is there a suggested/documented method for webhooks like mine to respond to publish events without creating an endless loop?