Troubleshooting
The board is out of date
The freshness check measures how long it has been since the website and Bullhorn were last in step, against a limit you set. It failing does not mean the sync is broken — it means the sync is not keeping up with the pace you asked for.
Freshness
What the check actually measures
<code>w3rp_sync_freshness</code> compares the time since the last successful run against the staleness you are willing to tolerate. That limit is yours to set, and the right value is a business decision rather than a technical one: an agency placing contractors within the day wants a much tighter figure than one recruiting for six-week permanent processes.
Set it to something you would actually act on. A limit so tight that it fails every afternoon trains everybody to ignore the warning, which is worse than not having it.
Causes
Why it would start failing
In the order worth checking.
- The connection broke. No successful run since it did. Check w3rp_connection first — freshness is downstream of it.
- The scheduler stopped. See the article on the sync not running. The board does not get stale on its own; something stopped updating it.
- The schedule is slower than the limit. If you sync hourly but expect freshness within fifteen minutes, the check is correctly telling you those two numbers disagree. Change one of them.
- Runs are failing rather than not starting. The run history will show errors. That is a different problem and worth a support bundle.
Recovery
Catching up
Once the cause is fixed, one run brings the board back into step — the sync asks what changed since the point it last reached, so a gap of a day does not mean a day of work.
wp w3rp sync run
wp w3rp sync statusIf a lot changed while the board was behind, a reconciliation makes sure nothing was missed. Run it as a dry run first to see what it would do:
wp w3rp sync reconcile --dry-run