• Resolved seekbeacon

    (@seekbeacon)


    Problem with an action intermittently firing and duplicating email. Using FluentSMTP, and on UA v4.11

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Uncanny Automator

    (@uncannyautomator)

    Hi @seekbeacon ,

    Would you be able to send us a link to a screenshot of your recipe with all details expanded? Usually we would see something like this if another plugin is setting the status of something twice; we have seen a few Woo plugins set order status more than once, for example, which is why we offer a variety of triggers so we can make sure something reliable is available.

    Can you also confirm that in your recipe logs that you see the recipe run twice? Or do you mean the recipe run only appears once i the logs but 2 emails still went out?

    Thanks

    Plugin Contributor Uncanny Automator

    (@uncannyautomator)

    Hi @seekbeacon , since it has been 2 weeks since the last update, we will go ahead and mark this as closed. Let us know though if you do still need assistance here.

    Thread Starter seekbeacon

    (@seekbeacon)

    Sorry for delay:

    This the recipe – https://prnt.sc/0iP71bwrwXNV

    The log shows that it always runs twice – example here https://prnt.sc/JDJxO-iitxfn

    We don’t use Woo

    Plugin Contributor Uncanny Automator

    (@uncannyautomator)

    Hi, sorry about the confusion there. The Woo reference was an example of when we typically see something fire twice–because there are some Woo plugins that set status, so we might see them double up.

    Your example might suggest the same situation, but it’s really odd that they’re running 8 seconds apart. Usually if it’s doubled up we would see identical times or within 1 second or 2.

    Is there any chance you could try this in a Staging environment with all plugins disabled except for Automator? That would help us assess if another plugin is causing the login to be recognized twice. Are you running any plugins that might hook into the login process?

    We haven’t seen the double run before with this particular trigger, so it’s likely something in the environment doing it. Testing without anything else active would help us confirm.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Duplicates’ is closed to new replies.