WP 5.2 Site Health reports afterpay_do_idempotency_cron_jobs failed to run

  • Resolved embercide

    (@embercide)


    5 years, 10 months ago

    This was logged under ‘site health’ as a performance issue:

    A scheduled event has failed
    The scheduled event, afterpay_do_idempotency_cron_jobs, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

    In case it is relevant, our site is currently using the default WPcron and not server cron

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Afterpay

    (@afterpayit)

    Hi @embercide,

    Thanks for sharing this log entry. The team will investigate possible causes for scheduled events failing and discuss potential improvements as required.

    The Afterpay idempotency cron is intended solely to retry network requests in the event of a timeout. Unless any transactional discrepancies have been identified it is probably safe to ignore the log entry.

    Thank you.

    Hi there, This cron is run every 7 seconds. Is there a reason why it has to be so often? My site has over 4000 hits on cron and wondering if the frequency needs to be this high or can I change it to a longer period.

    Cheers

    Steven

    • This reply was modified 5 years, 9 months ago by deepwebdesign.
    Plugin Author Afterpay

    (@afterpayit)

    Hi @deepwebdesign,

    Thank you for your comment.

    The idempotency cron is intended to activate only after a payment capture API call times out (after 7 seconds), then deactivate as soon as a response is received from Afterpay in any subsequent retry. Since 99.4% of payment capture requests are responded to by Afterpay within 7 seconds, and almost all within 70 seconds (10 retries), the short interval was not expected to have any noticeable impact. The objective is simply to provide more meaningful feedback to customers about the status of their transaction in the unlikely event that it takes longer than 7 seconds to process.

    If there is reason to believe the cron is not behaving as described above, please create a support ticket to facilitate a comprehensive investigation:
    https://help.afterpay.com/hc/en-au/requests/new?ticket_form_id=193406

    The team would be happy to provide any further technical assistance as necessary. This support is available to anyone experiencing technical challenges with the Afterpay Gateway for WooCommerce plugin.

    Thank you.

    Plugin Author Afterpay

    (@afterpayit)

    Hi @embercide and @deepwebdesign,

    Please be advised that the idempotency cron has been removed (in favour of extended initial timeouts) in the latest release, v2.1.0. This topic will therefore be marked as resolved.

    Thank you.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WP 5.2 Site Health reports afterpay_do_idempotency_cron_jobs failed to run’ is closed to new replies.