Scheduled actions are always a few hours behind

  • Thank you very much for your support.

    Our server gets updated and it seems the system time and the WordPress time are different now. The scheduled actions are always 4 hours behind and they won’t be able to run even after 4 hours.

    Is there any way we can fix this, maybe add an offset to the scheduled date? Please advise.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Jonathan Stegall

    (@jonathanstegall)

    I’m not sure. Generally the plugin does all of its scheduling in UTC rather than dealing with WordPress time. I think to help you with that I’d need to know where it’s getting a time based on your system or your WordPress install.

    Thread Starter dennisdit

    (@dennisdit)

    Thank you for checking.

    “Universal time is 2022-05-24 20:36:55. Local time is 2022-05-24 16:36:55.”

    This is the setting in WordPress. You can see the WordPress time (local time) is behind. All scheduled actions are using UTC, so they will never get to run and stay “pending” until the scheduled time has passed. The server time is changing from time to time. Is there any way we can add an offset to the UTC time?

    Plugin Author Jonathan Stegall

    (@jonathanstegall)

    I’m not aware of any way to do that. There was a bit of discussion about that on Action Scheduler’s GitHub some time ago, but it appears they decided not to do anything with it. Certainly, Action Scheduler designs the scheduled actions so that they run using UTC. I’m not really sure why the timezone WordPress is using would affect this. You might want to talk to your host about it.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Scheduled actions are always a few hours behind’ is closed to new replies.