Barry Hughes

Great! I agree it perhaps isn't as 'neat' as native support of some kind might be, _but,_ I'm also a little unsure just how often this sort of thing might...

> Shouldn't it be as simple as implementing your code into the relevant functions, and then done? Well, we could consider that, but my initial instinct is that although it...

This sounds like a valuable discussion and I definitely agree we could expand the range of options available for processing queues. > I believe adding ability like worker/watcher/listener is better...

Thanks for all the notes and ideas. We did do some light experimentation at the end of last year, and looked at a model involving a single queue server running...

The above, plus (depending on how things are configured) different types of problems [relating to cached values](https://github.com/woocommerce/action-scheduler/issues/790) can surface, and can be especially problematic in very long running processes.

Hi @kevin25, I'm just a little unsure if you mean you cannot currently access WP CLI, or if you *can* access it but don't see a way to accomplish your...

Thanks for sharing those links :-) We have some provisional plans to introduce a dedicated WP CLI command to clean-up actions (plus other mitigations to keep table sizes in check),...

Thanks for flagging this, @Nemi5150. > My guess is that there must be a race condition two requests are running at the same time and end up scheduling two upcoming...

Hi! > Would it be worth changing the scheduled action store status to failed/complete only after the call to schedule the next event was sent? Possibly. I think that would...

:memo: [PR #727](https://github.com/woocommerce/action-scheduler/pull/727) doesn't actually solve this, but it certainly seems to reduce instances of the problem (and so it may be all we actually need).