Action Scheduler showed one failed action (“no callbacks are registered”), with the queue otherwise showing mostly future-dated actions and no real backlog — which looked, at a glance, like the queue itself might be struggling. Separately, a recurring queue-processing event, due to run in seconds, disappeared from the list right after it ran, and trying to edit it afterward produced a message that it no longer existed — which looked like WordPress had lost or deleted it.
Reading a Cron/Queue Display Correctly Before Calling It Broken
Field Note #289
⚡ Quick Fix (TL;DR)
The Culprit: The failed action was an orphaned migration hook with no registered callback — a single stale entry, not evidence of a struggling queue. And the "vanished" event was simply a recurring event that ran and was rescheduled for its next occurrence, which is normal behavior for any recurring cron entry.
The Fix: Both were confirmed as non-issues by checking status, timing, and the next scheduled occurrence rather than treating either display change as a failure.
Rather not untangle this yourself? Our Done-For-You team handles exactly this kind of thing, start to finish.
See DFY options → Was this helpful? Thanks for the feedback!
Tagged in :