Bullhorn errors
The codes Bullhorn steps can stop a run with, each with its fix and what happened.
BULLHORN_AUTH
Test the connection under Manage → Connections.
Bullhorn refused the session.
BULLHORN_FILE_INVALID
Paste the file's base64.
The file contents are empty or not base64.
BULLHORN_FILE_TOO_LARGE
Fetch it outside the flow.
The file is larger than a run can carry.
BULLHORN_FORBIDDEN
The API user lacks the entitlement for it.
Bullhorn refused the call.
BULLHORN_INVALID_BODY
Give Bullhorn the fields as a JSON object.
The record body is text or empty.
BULLHORN_INVALID_CURSOR
Paste its Next cursor, or clear it.
The cursor is not one a Bullhorn list answered.
BULLHORN_INVALID_RESPONSE
Check the connection.
Bullhorn answered something that is not JSON.
BULLHORN_INVALID_SEGMENT
Remove /, ? or #.
A name or id contains a character that would address a different record.
BULLHORN_NOT_FOUND
Bullhorn has no record by that id.
BULLHORN_NO_SESSION
Test it under Manage → Connections.
This connection has no Bullhorn session yet.
BULLHORN_REQUEST
Its own reason is in the detail.
Bullhorn refused the request.
BULLHORN_RESPONSE_TOO_LARGE
Ask for fewer fields or a smaller page.
Bullhorn answered more data than a run can parse.
BULLHORN_THROTTLED
Wait a moment and run it again.
Bullhorn is throttling this workspace.
BULLHORN_TOO_MANY_ROWS
Narrow the query, or page the request.
Bullhorn returned more rows than a run can carry.
BULLHORN_UNAVAILABLE
Try again once it is back.
Bullhorn could not be reached.