Barry Hughes

Hi @piotrbak, We did consider this point, but decided to ship and see what feedback might come in—thank you for sharing—since in some cases this may be less of a...

> Maybe the async action could be treated as past-due after a specific time since it was created? That's a possibility, and is probably the best course of action (though...

> This will make sure that we will only compare when the field has a value on it. Well, this would be a breaking change. Consider the following snippet—a plugin...

As a general position, the nature of Action Scheduler leads me to strongly err on the side of backwards compatibility—since it is not uncommon for plugin A to ship with...

...At the risk of going a little off-track, it also occurs we could support more complicated date queries: ```php as_get_scheduled_actions( [ 'date_query' => [ [ 'date' => '2020-01-01 00:00:00', 'compare'...

> ...so this will return the completed scheduled actions before now + completed scheduled Async actions and will not get the pending Async tasks anymore. Gotcha, makes sense :+1: >...

Thanks for the information, @alewolf. We can replicate and will look at possible solutions. For now, can you run your code on a later hook such as `init` itself (at...

Hi @Mte90, I could certainly see the value in that. I'll mark this as a low priority enhancement and, if you wish, you could submit a PR to add this...

I don't believe we currently define or look for any top-level constants (except for some that are defined by WordPress or WP CLI), so there isn't really any precedent to...

Same; Ventura 13.0 | Vagrant 2.3.2 | Virtual Box 7.0.2.