Documentation
Diagnostics and support
The plugin adds its own checks to WordPress Site Health, so most problems announce themselves in a place you already look. This page explains what each check means and what to do about it.
Checks
The health checks
Tools → Site Health → Status.
| w3rp_connection | Can the site reach Bullhorn and is the authorisation still good? A failure here explains almost everything else |
|---|---|
| w3rp_cron | Is WordPress’s scheduler running? If your host disables it, the sync will not run on its own |
| w3rp_sync_schedule | Is a sync actually scheduled? A schedule that is set but not registered is the quiet failure this catches |
| w3rp_sync_freshness | How long since the board was last in step with Bullhorn, against the staleness you allow |
| w3rp_delivery_backlog | Are applications queued but not being delivered? |
| w3rp_permalinks | Is the permalink structure one that job pages can use? Plain permalinks break the board |
| w3rp_tables | Are the plugin’s own database tables present and current? |
WP-CLI
Running the checks yourself
The same answers, from the command line.
# All checks, as a report.
wp w3rp diagnostics
# The Bullhorn connection state.
wp w3rp bullhorn binding-state
# Has Bullhorn's API changed under us? Exits non-zero on a breaking verdict.
wp w3rp bullhorn drift-checkThe drift check is the one worth putting in a monitor. It exits non-zero when the verdict is breaking or when the check could not be completed, so it works as a scheduled job without anybody parsing its output.
Getting help
What to send us
The support bundle, and why it is better than a description.
The plugin can produce a support bundle: the diagnostic answers, the recent run history and the versions and counts it is prepared to disclose, gathered in one file. Sending that with your question removes a round trip of us asking which WordPress version, which PHP, when the last sync ran and what the connection says.
- What it contains. Versions, what is present, counts and the verdicts of the checks. Deliberately boring.
- What it does not contain. It is an allow-list, not a redaction pass: no secret values, no applicant or candidate data of any kind, no error messages from Bullhorn (which can quote the record that caused them), and nothing typed into a free-text setting. A fact that was not listed when the bundle was written is not in it.
- Read it before you send it. It is yours, and you are entitled to know what is in a file you are sending. Open it.
Before you contact us, check the connection
A failing <code>w3rp_connection</code> check explains most symptoms people report: roles not appearing, roles not updating, applications queuing. Bullhorn access can be revoked or changed at the Bullhorn end without anyone telling the website, so start there.