Barry Hughes

Related reports: - https://github.com/woocommerce/action-scheduler/issues/958 (closed in favor of this one) - https://github.com/woocommerce/action-scheduler/issues/856 (not identical, but has some cross-over)

Another report: https://github.com/woocommerce/action-scheduler/issues/986

Yep ... that's a perfectly reasonable approach (in fact, it is *essentially* what Action Scheduler tries to do, except in various cases it does not have permission).

Internal discussion: p1690905319416299-slack-C3L7CFBRV

@eddr since you are creating a WooCommerce extension, you can presumably depend on WooCommerce being present (or can test for it). WooCommerce includes its own copy of Action Scheduler, and...

Gotcha ... in that case, I don't have an easy workaround I can share. I've updated the issue title and description, though, to create a task for cleaning things up...

> Any idea what's causing this? Well, really any of the same possibilities outlined in #882. > Could you add a safeguard not to let it run into a fatal...

Hi @skinnycat-software, Yes, this is a problem (cron scheduling is based on UTC, so there is an apparent shift of one hour as sites enter and leave DST) and essentially...

https://github.com/woocommerce/action-scheduler/pull/907 has been merged and introduces `wp action-scheduler clean`.

Thanks, @lsinger 👋🏼 ... re-opening.