Troubleshooting
The sync has not run
Not "a role is missing" but "nothing has happened since Tuesday". Two health checks cover this between them, and the usual culprit is hosting rather than the plugin.
Diagnose
The two checks to read
| w3rp_cron | Is WordPress’s own scheduler working at all? If your host has disabled it, nothing scheduled runs — not just this plugin |
|---|---|
| w3rp_sync_schedule | Is a sync actually registered to run? A schedule that is set in the interface but not registered is the quiet failure this catches |
wp w3rp diagnostics
wp w3rp sync statusThe usual cause
If WP-Cron is disabled on your hosting
Common on managed WordPress hosts, and sensible of them.
WordPress triggers scheduled work on page views, which is unreliable on a quiet site, so many managed hosts turn that off and run a real system cron instead. If yours has done that and nothing was set up for this plugin, the sync will never fire on its own.
The fix is a system cron calling WP-CLI on whatever schedule you want. Your host or developer will know the exact form it takes on that platform; the command is:
wp w3rp sync runThe background queue also needs processing where the scheduler is disabled, which is <code>wp w3rp queue run</code>.
Stuck runs
If a run started and never finished
A sync takes a lock so that two runs cannot work at once and produce duplicates. If a run is killed mid-flight — a timeout, a deployment, a fatal error elsewhere on the site — the lock can outlive it, and later runs will coalesce rather than start.
A coalesced run deliberately records nothing, so the health check cannot be fooled into reporting the sync as healthy when it is actually stuck. If the Sync screen shows nothing happening and no errors, this is the case to suspect. Tell us and send a support bundle rather than guessing: the recovery depends on where it stopped.