Action Scheduler Failed x thousands

  • Resolved bighippo999

    (@bighippo999)


    4 years, 6 months ago

    I’ve noticed when checking through our store the action scheduler jobs for ‘wc_facebook_regenerate_feed’ are failing.

    2020-06-02 19:35:38 +0000
action created
2020-06-02 19:36:24 +0000
action started via Async Request
2020-06-02 19:37:58 +0000
unexpected shutdown: PHP Fatal error Maximum execution time of 60 seconds exceeded in /mnt/www/ukcophumour.co.uk/wp-content/plugins/facebook-for-woocommerce/includes/fbutils.php on line 405

    We have thousands of these errors and

    2020-06-02 19:29:47 +0000
action created
2020-06-02 19:30:28 +0000
action started via WP Cron
2020-06-02 19:35:37 +0000
action timed out after 300 seconds

    We’re running WooCommerce 4.1.1 on WordPress 5.4.1 and plugin version 1.11.3
    Database wise, we have 2G data, 912 products with 39600 variations and over 53k orders.
    PHP time limit is 600 seconds and we run Redis object cache.

    Is anyone else getting high fail’s in the action scheduler? (WooCommerce>Status>Scheduled Actions>Failed)
    We mostly see ‘Maximum simultaneous queues already in progress (1 queue). No additional queues will begin processing until the current queues are complete.’ when opening the Scheduled actions, but occasionally it’s counting down to the next job. The concern is, this may be blocking other jobs?

    Thanks,

Viewing 4 replies - 16 through 19 (of 19 total)
  • Thread Starter bighippo999

    (@bighippo999)

    @bobpassaro I think it’s against rules to post other plugin links, and I don’t fancy being in moderator jail for 6 months again. So I’d suggest a search for “woocommerce feed” and see what’s available that may suit your setup. We run with about 800 products but behind those are thousands of variations. Like you we had memory errors and no matter how much we threw at it or how much time we increased to just couldn’t get passed the errors. The previous version we ran at least seemed to push new products straight to facebook, but the regular jobs always failed. When the immediate push was removed in place of the regular job we seemed to have nothing new reaching the facebook catalogue.
    Like you I think it may be fine if you’re running a smaller store with less items but it just didn’t work for us.

    bob.passaro

    (@bobpassaro)

    @bighippo999
    Right, got it. Thanks! I will poke around a little more. Still hoping to hear back from SkyVerge on this. Any ideas, SV? I feel like it’s something going wacky with the job queue and not so much the actual code that make the api request to FB, etc. But I still haven’t figured out the exact root of the issue.

    Julie Martin

    (@julieskyverge)

    Hi @bobpassaro,

    As this topic is resolved, and to keep with forum guidelines, can you please open your own topic with a paste of your system status so I can get a better idea of what might be going on? You can grab it by going to:

    WooCommerce > Status?and clicking on?Get system report.

    Additionally, any screenshots that might illustrate the issue would be great!

    Thanks so much,

    Julie ??
    SkyVerge
    (PS: Thanks @bighippo999 for chiming in!)

    I didn’t get it, what is the solution? I’m getting the same timeout after 300s, and probably because my store has thousand of products.

Viewing 4 replies - 16 through 19 (of 19 total)
  • The topic ‘Action Scheduler Failed x thousands’ is closed to new replies.

Tags