- Support forum for the Automated Order Status Controller for WooCommerce.
- This topic has 8 replies, 2 voices, and was last updated 4 hours, 10 minutes ago by
.
-
Posts
-
I am using the Action Scheduler to run order status changes every 30 minutes. Many times the statuses don’t change even though this action has supposedly run many many times.
If you go to an order, you see this kind of message:
Status scheduled to be updated from
CompletedtoShipped(Rule #3: Shipped) on April 11, 2024 3:16 pm (i.e., now). Current time is April 12, 2024 10:15 am.So in this case the status should have changed 17 hours before and had 34 opportunities to do so.
Is there any fix for this? When I run alg_wc_order_status_rules_process_rules_as manually, it seems to find the forgotten orders and update them correctly. Obviously I want this to be automated and not require me to manually run the action.
Hi there,
In such a case, please go to the “Advanced” section and set the “Non-matching order status history” to “Use latest record anyway”. Please give it a try.
Since this hasn’t been working, I wanted to try adding it to my server’s cron jobs. Can you tell me what I put for the command? Is it just:
https://[sitenamehere].com?alg_wc_order_status_rules_process_rules
Hi Lisa,
If you want to initiate all rules processing by URl, then please go to the “Advanced” section and enable “Allow rules processing by URL” and then you can access the URL link listed there and run the rules.
Kin regards.
Never mind – the cron job I had set up is running. But the orders still don’t resolve to their correct statuses (some do, sometimes?). I get the same message on the order:
Status scheduled to be updated from
CompletedtoShipped(Rule #3: Shipped) on April 22, 2024 8:06 am (i.e., now). Current time is April 29, 2024 12:52 pm.Hi there,
We were unable to reproduce the issue. Would it be possible to share the WordPress dashboard access so that we can check the issue closely? The please send us the login details to [email protected].
Kind regards.
- You must be logged in to reply to this topic.