It’s not uncommon for WP Cron to occasionally show a few past-due actions since tasks might not always execute exactly on time. However, seeing a large number (like 155) may indicate an issue with the scheduling system.
Can you navigate to WooCommerce → Status → Scheduled Actions → Pending and manually run any pending actions to see if this clears some of the backlog:
It may also be helpful to review any recently added plugins that might impact cron tasks, as conflicts with scheduling plugins can sometimes cause delays. Temporarily deactivating them may reveal if one of them is the source of the issue.
This guide on debugging WP Cron might also be helpful: Debugging WP Cron.
I have just checked the status. It shows 598 past-due actions. Don’t know what’s going on. I haven’t updated any plugin AFAIK. This problem starting to show from last few days out of nowhere.
Thank you for sharing more details about the issue.
To clarify, are you still seeing the pending action even after running it manually? Additionally, have you set up a server-level cron job by disabling WP-cron? Also, have you had a chance to manually disable all plugins to see if the number of past-due actions decreases?
It would also help us to review your current System Status Report to gain more insight into your setup. You can find this report in your WooCommerce dashboard by going to WooCommerce > Status. From there, please select Get system report and then Copy for support.
If there are any fatal error logs, please share those as well. These can be accessed under WooCommerce > Status > Logs.
Once you’ve gathered this information, please paste it into a Code block in your reply or use pastebin.com and share the link with us.
I understand that the problem lies with Cron. For further troubleshooting, I recommend installing a 3rd party plugin WP Crontrol. It will provide us with more details about the underlying issues.
Please share screenshots of the issues that you find after installing WP Crontrol.
I have installed the WP Control and checked the cron events. There are some past due events. When I try to run it manually, it creates another job (same) with 54 years past date.
