• Resolved soulfoxconsulting

    (@soulfoxconsulting)


    Hello,
    we have a gravity form submit as trigger.
    As action we add a subscriber to mailpoet.

    The action do not really complete every time.

    What could be the reason? How can we debug this?

    Thanks in advacnce,
    Maik
    PS: I tried to add a screenshot. Not sure if it is displayed correct.

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

    (@uncannyautomator)

    Hi @soulfoxconsulting ,

    Sorry to hear about the issue.

    Screenshots would really help here, specifically of the recipe (with all details expanded) and records from Automator > Logs for the recipe, just in case there’s an issue showing. Perhaps you could upload the screenshots somewhere and paste a link here.

    It could be as simple as you using a Logged-in recipe type instead of an Everyone recipe, as that would then only fire for users that are logged in at the time the form was submitting. Seeing context from the screenshots would help, as well as any differences you can see from recipe runs that were successful vs. ones that weren’t.

    Thanks

    Thread Starter soulfoxconsulting

    (@soulfoxconsulting)

    Hello,

    i try to paste some links here:
    Recipe Screenshot: https://share.soulfox.consulting/gZx5tCb48tbLzmCgRSmM

    Screenshot of the log with the message:
    https://share.soulfox.consulting/YqGsHBq6QHw7xBy9xYPS

    The difference to the logs when everything is working is the notice:
    Waiting for the action to be completed

    Hope that helps,
    Maik

    Plugin Contributor Uncanny Automator

    (@uncannyautomator)

    Thanks, that is unfortunately a more difficult issue.

    For context, when we run that MailPoet action, we need to offload things to a background cron (a scheduled task) that processes that actions. Normally it shouldn’t take long, but in your case it seems like maybe there’s an issue with the cron.

    It might be worth trying the WP Crontrol plugin (https://www.ads-software.com/plugins/wp-crontrol/) to see if any cron issues are reported. If there are, seeing a screenshot of errors here would help. It would also be great if you could send us a system report (after removing URLs) from Automator > Status.

    If those don’t yield clues, we may ask for more details via the help desk on our site.

    Thread Starter soulfoxconsulting

    (@soulfoxconsulting)

    Hello,
    i looked in the cron logs and did not see any errors that seem to be in connection to automator.

    In addition i send you the system report without urls. I replaced them with xxx. I add the system report to download here:
    https://cloud.soulfox.consulting/index.php/s/mp7y4t4ryYgrEGN

    Do you need something else?


    Plugin Contributor Uncanny Automator

    (@uncannyautomator)

    Hi @soulfoxconsulting ,

    Our developers reviewed your update and wondered if you could search for “automator_mailpoet_subscribe_to_list” in WP Crontrol and send us an image of what’s shown; it may be stuck (like an incorrect date) and that may not show as an error. While you could try triggering it manually to process anything currently stuck, seeing the date and details would help us assess what might have happened and how we could prevent it from happening again in future.

    Thread Starter soulfoxconsulting

    (@soulfoxconsulting)

    Hello,

    i looked inside the Cron and made a Screenshot: https://cloud.soulfox.consulting/index.php/s/aszPtbmyxSgnFQC
    Not Sure if that is the one you want.

    At the moment i can not reproduce the error.

    Inside the database, table=actionscheduler_logs i saw maybe something “strange”. A Switch from Async Request to WP Cron? Maybe that makes the little difference?
    https://cloud.soulfox.consulting/index.php/s/CFANotnZHdByQPL

    Hope that helps to come to an idea ?? .

    Have a great day,
    Maik

    Plugin Contributor Uncanny Automator

    (@uncannyautomator)

    Sorry about the delay here.

    Our developers had a look at what you sent, but they noted that it was related to Action Scheduler, rather than just standard crons. This particular action does just use normal crons on the Automator side. The ones in the first screenshot are actually entirely on the MailPoet side, not Automator (yes, the “automation” references sound like Automator, but those are related to MailPoet).

    Any cron details would still help, but we wondered if maybe we could get a bit more data from you about the site via our Help Desk rather than this channel, so that the details aren’t public.

    Thanks

    Thread Starter soulfoxconsulting

    (@soulfoxconsulting)

    Hello,

    thanks for the reply.
    I will send you a message over helpdesk together with a link to this conversation.

    Thanks,
    Maik

    Plugin Contributor Uncanny Automator

    (@uncannyautomator)

    We’ll tentatively mark this as closed since this has moved to our Help Desk for additional debugging.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Action not completed’ is closed to new replies.