Prevent posts duplication on Social Media when on post edit

Hi @rrose1311 ,

We’re really sorry about the delay here.

Okay, our team wondered if perhaps you’re using the “User’s post is set to a specific status” trigger, which would fire when a post is updated. The trigger for “A user publishes a?type of?post with?a taxonomy term?in?a taxonomy”, on the other hand, only fires when it’s initially published and sounds like what you should be using (it doesn’t require that any taxonomy be set).

Seeing the recipe would definitely help us concern.

Another possible workaround if you do need to go by status would be to add an action to add some kind of post meta value as a flag, then add a condition to the action to see if that meta value exists. Then, if the recipe is triggered later, the action wouldn’t run because it would see the meta flag from the last run and skip the action.

Hi and thanks for your reply,
this is the current setting of my recipe:

I am using the free version of the plugin, so it seems that I cannot access the trigger you mentioned. Could this problem be related to the free version or do I need to modify my current configuration with other triggers or actions?

Thank you!

Hmm… no, your trigger is appropriate here.

Let’s just confirm:

1. A user publishes a blog post for the first time. The recipe runs.
2. The same (or another?) user edits the post in #1. They make some changes.
3. The user clicks the Update button. The recipe runs again.

That’s exactly what you’re doing, so no other plugins involved for posting/updating, that’s the exact test case? Your recipe looks fine.

My workaround would solve things for you, but that example does require Pro. Let’s confirm the exact test case first, as in our test that trigger did work the way you want it to. Next we may request a system report, but let’s sort out the exact test case first.

Hello and sorry for the late reply,

I can confirm that the test case is this:

1. A user publishes a blog post for the first time. The recipe is executed.
   
2. The same user or another user edits the post in #1. They make some changes. This also happens if another user edits the post several times, the recipe is executed one more time.
3. The user clicks the Update button. The recipe is executed again.

Thanks!

Hi @rrose1311 , we tested again, but we cannot reproduce this on our side. Now, if the person updates the post to a Draft or other status first, then publishes it again, that would cause the recipe to fire more than once. But if this just an update to a published post, as you describe, the trigger you’re using wouldn’t cause it. Is there any way at all the user or a plugin could be changing the status before it’s updated?

Otherwise, it probably would be helpful if this could be tested on a Staging site with all plugins except Automator disabled, just to rule out some other plugin causing it (and just switch the action to sending an email so you’re not posting too much and so it’s easier to track).

If it’s still happening with only Automator active, I think we would need to take a closer look if it’s possible with direct access, but for that type of thing it would be safer to reach out via our website.

Hi and sorry for the late reply,

I think then that it is possible that the editor plugin installed on our site changes the status of the post to draft status before it is republished. Thanks, I think I was missing this information regarding the status!

Yes, that would definitely do it. Thanks for confirming!

We’ll go ahead and mark this as resolved for now.