Admin and diagnostics
Set it up, watch it run, and know why when it does not
The connection is set up from the WordPress admin, and everything it does afterwards is visible there: the last run, the next run, what changed, and what failed. When you do need help, the information we need is already collected.
For the person who gets the call when a job is missing.
| Started | Result |
|---|---|
| 09:14:02 | 34 changes |
| 09:09:01 | No changes |
| 09:04:00 | 3 submissions |
| Started | Trigger | Duration | Result |
|---|---|---|---|
| 09:14:02 | WP-Cron | 6.2s | 34 changes |
| 09:09:01 | WP-Cron | 5.4s | No changes |
| 09:04:00 | WP-CLI | 2.1s | 3 submissions |
| 08:59:02 | WP-Cron | 1.3s | 1 skipped |
The problem it solves
A job is missing and nobody can say why
The consultant says they published it. The website does not have it. Without a record of what ran and what it did, the next hour goes on guesswork, and the answer is usually "try again and see".
A silent integration
Guesswork, then a support ticket
- No record of what ran, or when
- Failures that stop quietly
- Errors written for developers, if written at all
- Nobody can check without database access
With W3Bullhorn
An answer in the admin, in a minute
- Last run, next run and what changed
- Run history you can look back through
- Failures said in plain language, and flagged
- A support bundle with the detail, and nothing sensitive
Setting it up
Connected from the admin, not from a config file
Your Bullhorn credentials are entered once, in the WordPress admin, and stored encrypted on your own server. The set-up walks through the connection and tells you plainly if the account is missing something, rather than failing later with a code nobody recognises.
- Set up from the WordPress admin
- Credentials encrypted on your own server
- A clear answer when the connection is not ready
- Reconnect without touching the rest of the configuration
Specification
What it supports
What the person who supports the site will ask.
| Set-up | Connection and settings from the WordPress admin; no configuration files to edit |
|---|---|
| Sync status | Last run, next run, and what changed on each: imported, updated, closed |
| Run history | Kept so a past run can be looked at, rather than only the most recent one |
| Failures | Reported in plain language and flagged, instead of stopping silently |
| Applications | Delivery into Bullhorn visible too, so a missing application can be traced |
| WP-CLI | Resyncs, one-off pushes and scheduled maintenance from the command line |
| Support bundle | The detail we need to help, with credentials and candidate data kept out of it |
Boundaries
What the admin tools do not do
-
They are not a Bullhorn admin console
Your Bullhorn configuration is changed in Bullhorn. These screens show what the website is doing with it.
-
They do not send us your data
What is on these screens stays on your site. A support bundle is produced only when you choose to send one, and leaves credentials and candidate data out.
-
They are not a monitoring service
The plugin tells you when a run fails. Watching your hosting, uptime and backups is a separate job.
W3Bullhorn is an independent product. It is not affiliated with, endorsed by or sponsored by Bullhorn, Inc. Bullhorn is a trademark of its owner.
FAQ
Questions about admin and diagnostics
Short answers here. Anything else, ask us directly.
Related features