Post update send webhooks twice

Hey @nforgeot – Thank you a lot for your message, as well as for using our plugin.
If WordPress or any plugin updates the post within the code multiple times, the webhook also gets sent multiple times, depending on the amount of updates.

Luckily with our new version 3.3.0, we introduced a feature that allows you to limit webhook calls of the same nature within the same WordPress instance.
To use it, simply head over to your added “Send Data” URL, open the settings, and make sure to check the “Fire only once per instance” setting.

@nforgeot Did this help option help you? I have the same problem running the 3.3.0 and enabled the “Fire only once per instance” option and it’s still coming through twice. I’m wondering if it’s to do with METABOX or ACF which I’m also running but deleted these fields from the post type.

Hmm, I think this could be Gutenburg switched back to classic and we’re all good. Would be interested if anyone else has the same experience.

Hey @jasongreenlees – That’s a great question – This issue might appear due do Gutenberg. I assume they re-save the post via ajax, which is a separate WordPress instance that is always considered a separate call.
We are already planning an implementation to address this issue.

I have the same issue of webhook response being duplicated on post published or post updated with Guttenberg. When will this be fixed?

Also switched back to the classic editor and works as expected.

Yes, I also tried switching to classic editor and there is no duplication.

Hey @dmwalk @jasongreenlees – What appears as an issue is just the right thing to do for our plugin as Gutenberg really creates the post first and then changes the status. This happens due to Ajax. We added so far a filter that can limit the execution of the same action to one time within the same instance, but with Gutenberg, the second requests happens via ajax, so for any kind of plugin it would appear as a separate request.

To fix that, I could currently only thing of a secondary check using our Flows feature of the pro version (as it allows conditioning).
We are planning to implement our Flows feature into this free version, but this requires some more time due to guidelines and other regulations.

I’m having a similar issue too not sure if it could be the Gutenberg, but in my case it only sends drafted post doesn’t send published ones, please how can I fix this?

Hey @adeshinex – please do open another support task for future issues.
Within the settings of the URL you added to the webhook, you can select the status and post type of the posts you want to send the webhook for.
Simply select your desired values there.

This double firing with Gutenberg seems to still be not fixed. When are you going to fix it?

Hey @dmwalk – Thanks for reaching out. I can confirm that we are still on the new release to bring in compatibility with all of our recent changes. This next release will contain a more significant rework regarding the functionality of the free version, so we have to make sure that everything works as expected.