• CmdrKeene

    (@shawnkeenegmailcom)


    I have a site where the Action Scheduler has gotten stuck because of the TaxJar plugin. Several scheduled action calls in December (on the 3rd and 23rd) failed to run because TaxJar included too many chars in the list of IDs (I believe the limit is 190 and these were variable but all 250 or so).

    WordPress/Jetpack support helpfully included this information about how I was able to find the problematic actions and remove them in a staging copy of my database. But I’ve not done this on production yet, and

    Before version 3.0 the old scheduled actions are stored in the posts table with the custom post_type of scheduled_action and the post_content would serve as the $args for migration.

    This means that we could run an SQL query on the staging site(since it’s a copy of the live site) and find all of the scheduled action posts which have a post_content > 190 characters.

    SELECT * FROM wp_posts WHERE post_type= 'scheduled-action' AND char_length(post_content) > 190

    If that returns a list of entries in the table, those are the offending scheduled actions preventing the migration from completing.

    You can point the developers to this issue for more information:

    https://github.com/woocommerce/action-scheduler/issues/418

    I have found there were 6 failed actions. Here’s one, but the others were basically the same.

    "59525","0","2019-12-23 11:58:57","2019-12-23 17:58:57","{""queue_ids"":[1975,1976,1977,1978,1979,1980,1981,1982,1983,1984,1985,1986,1987,1988,1989,1990,1991,1992,1993,1994,1995,1996,1997,1998,1999,2000,2001,2002,2003,2004,2005,2006,2007,2008,2009,2010,2011,2012,2013,2014]}","taxjar_process_record_batch",,"publish","open","closed",,"scheduled-action-5e010083e6d795.01231434-FPeY3Rsy50rrx66ZRWXbQrcgc4SljQkX",,,"2019-12-23 11:59:31","2019-12-23 17:59:31",,"0","https://website.com/staging/1038/?post_type=scheduled-action&p=59525","0","scheduled-action",,"3"

    I’m reporting the problem here in hopes to fix the issue or possibly guidance as I seek to rectify the problem on my production site.

Viewing 1 replies (of 1 total)
  • Thanks for reporting this issue. This has been resolved on version 3.0.14 of the plugin, which fully supports Action Scheduler 3.0

Viewing 1 replies (of 1 total)
  • The topic ‘Action Scheduler Problem’ is closed to new replies.