Unable to import historical data

  • Resolved Agence Larsen

    (@arsenelesueur)


    1 year, 8 months ago

    Hello,
    For some time I’ve had expired planned actions piling up… and I noticed that the data import process for WooCommerce statistics kept looping.

    When I stop the process and restart it manually (after deleting the transients and the stats cache) I systematically get the error “The response is not a valid JSON response.” when I click on “Start”. I get the same response when I click on the button next to “Delete previously imported data”.

    I don’t know what to do. Unfortunately, the statistics no longer work and my colleagues can’t use the WooCommerce application on their smartphones, which is very annoying.

    Do you have any idea how I can find the source of the problem and fix it?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Agence Larsen

    (@arsenelesueur)

    1 year, 8 months ago

    Just a quick update, I’ve seen that the table “prefix_action_scheduler_logs” is growing incredibly fast on my database.

    I have an incredibly long list of the same entry (about 30M) :
    log_id ==> 0
    action_id ==> 0
    message ==> action ignorée via WP Cron
    log_date_local ==> 2023-10-17 21:01:30 (I have about 15 entries per second)
    log_date_gmt ==> 2023-10-17 23:01:30

    I hope that it will help you seeing what is happening to me 🙂

    Thread Starter Agence Larsen

    (@arsenelesueur)

    1 year, 8 months ago

    The problem has been solved !

    All entries in the wp_actionscheduler_actions table had “0” as “action_id“… and all entries in the wp_actionscheduler_logs had a value of “0” for log_id and action_id so we did the following steps :

    1)emptying the ****_actionscheduler_logs table (which kept growing fast but a bit lighter)

    TRUNCATE wp_actionscheduler_logs

    2) cleaning all complete, failed and canceld actions from the wp_actionscheduler_actions table 

    DELETE FROM wp_actionscheduler_actions WHERE status IN ('complete','failed','canceled')

    3) renaming the table to ****_actionscheduler_actions2 and applied a “fix schema”.

    ==> Then the table was regenerated with correct action_id values, which launched the list of pending planned actions that were blocked, and enabled the import of historical data from WooCommerce to be launched correctly.

    hrn1995 (woo-hc)

    (@aguinaldodarla)

    1 year, 8 months ago

    Hi @arsenelesueur

    Apologies for the delay in our response. We have a recent influx of support requests and are currently working through a backlog. We’re glad that you are able to figure this out. You did well! We also appreciate you sharing the solution with us.

    Please don’t hesitate to start a new topic if you have any more questions down the line.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Unable to import historical data’ is closed to new replies.