Aleksandar

Hi @jorgeatorres Sure. I'm running it on the `woocommerce_init` hook. Also `as_enqueue_async_action` works just fine. It's only `as_has_scheduled_action` that provokes the error.

> For now, can you run your code on a later hook such as init itself (at default priority 10 or higher)? Thanks, I already found a different workaround for...

This has not been added to the documentation yet. Is there a particular reason? Would you accept a PR that adds it to the docs?

I face the same issue (also working locally and not working on Heroku)

I figured out the problem in my case. I had a bug in the code which, under certain conditions didn't add a `to` address. Interestingly it was working fine locally....

When checking for a non-existent category like `wp plugin check hello-universe --categories=nonexistent_category`, there is no fatal error. It just doesn't run any check. Should PCP show a warning?

Hi @barryhughes > Are you quite sure the problem is specifically tied to [3.7.4](https://github.com/woocommerce/action-scheduler/releases/tag/3.7.4)? This was a fairly [minimal set of changes](https://github.com/woocommerce/action-scheduler/compare/3.7.3...3.7.4). What version did you switch to, and have...

> What prevents you from using the WC Queue, or from using WooCommerce's copy of Action Scheduler directly (vs bundling your own)? Good question. Technically the Pixel Manager can also...

@davidperezgar I would, if the tests would show whats wrong.

@davidperezgar What conflicts? Speficics please.