Troubleshooting
Jobs are not updating when we change them in Bullhorn
The role is on the site, but a change made in Bullhorn has not followed. Three causes cover almost every case, and the third one surprises people.
Timing
1. The next run has not happened yet
Changes follow on the schedule, like new roles do. Check the last run time on W3Bullhorn → Sync before assuming anything is broken, and force a run if the change is urgent.
wp w3rp sync runFields
2. The field is not one the page shows
A field only reaches the page if it has been enabled.
If the change was to a field that is not enabled, the site is not ignoring the change — it was never asked to show that value in the first place. Open W3Bullhorn → Fields, or Field mapper if you have Pro, and check whether the field is enabled and placed.
Record tracking, under Advanced, shows where a value on the page came from. That turns "is it Bullhorn or the website?" into a lookup rather than an argument.
Edits
3. Somebody edited the job in WordPress
The one that catches everyone.
Bullhorn is the source for the fields it owns. If someone edited a job post directly in WordPress — to fix a typo, say — the next sync brings Bullhorn’s version back, because that is the whole point of having one source. Make the correction in Bullhorn instead and it will stick.
Anything the plugin does not own on that page is left alone, so this only applies to the fields that come from Bullhorn.
If nothing is updating, check the connection
A role that has not changed at all since a particular date, alongside other roles doing the same, usually means no successful run has happened since then. Start with the <code>w3rp_connection</code> check rather than investigating individual jobs.