Barry Hughes

Placing on hold while we watch for the outcome of the following upstream reports: - https://github.com/deliciousbrains/wp-background-processing/issues/107 - https://core.trac.wordpress.org/ticket/58566

Looks like a fix should land in [WP 6.5](https://core.trac.wordpress.org/ticket/58566). Let's keep this open (for visibility) until then—after that we can close.

Hi @galbaras, It doesn't feel inaccurate to me (in these cases, the action has indeed been marked as failed after 6,000 seconds have elapsed) but perhaps we could tweak the...

> The cleaner doesn't seem to run after 10x the time. Right, but it doesn't reflect when the cleaner itself runs: instead it is used to form the cutoff time...

> Since I sent the time limit to 600, wouldn't the task have died after 600 seconds already? No ... if we're talking about the same time limit, this is...

@galbaras—though you closed this, I think you may be right that the message is not as clear as it could be (if you found it confusing, probably others will). Would...

Thanks! > While we're on this, I've found nothing in the PHP logs Yep, there's no guarantee that the logs will contain useful information—they may contain nothing of interest at...

> Rank Math data fetches from Google Could be worth flagging with the Rank Math team? They can probably provide guidance on further debugging in relation to the actual action...

The backtrace in the original comment shows WooCommerce is present (which itself periodically ships schema updates). I'm curious why Action Scheduler's updates in particular aren't sticking.

Unfortunately, `wp action-scheduler fix-schema` will report success even if it did not manage to actually update the schemas. My guess here is that your database user has not been granted...