Permissions:

Product tier: Available for Expert subscription tier with HRIS Link add-on

While HRIS Link prefers to sync data endlessly, sometimes errors occur. HRIS Link errors serve to inform you of the cause of the problem and the suggested solution. Some errors are blocking errors, meaning updates to information in Greenhouse Recruiting won't occur without resolving the error first.

Greenhouse Recruiting sends a status email each time HRIS Link runs to confirm whether the sync succeeded or failed. If HRIS Link fails, the email will contain an error. Check out the table below to find the error name from your email, along with whether it's a blocking error, and how to solve it:

Email subject Error name
HRIS Link: User import completed with errors User email; email taken: <email address>
HRIS Link: User import completed with errors Missing required field: email, first/last name, or employee ID
HRIS Link: User import failed Server broke connection

User email; email taken: <email address>

Email subject HRIS Link: User import completed with errors
Error information User email; email taken: <email address>
Issue

The employee ID and email address for a given employee included in the HRIS Report are linked to two distinct Greenhouse Recruiting users.

For example:
HRIS Report Employee ID: 12345
HRIS Report Email Address: test@example.com

Greenhouse user 1 Employee ID: 12345
Greenhouse User 1 Email Address: test123@test.com

Greenhouse User 2 Employee ID: 01234
Greenhouse User 2 Email Address: test@example.com 

Blocking error? No, this is not a blocking error.
Solution
  1. Audit your Greenhouse Recruiting users to determine which users are tied to the employee ID and email address included in the HRIS Report. This can be done by exporting your entire user base via Configure Configure-icon.png > Users, or by using the employee_id or email parameter with the GET: List Users Harvest API endpoint.
  2. Cross-reference the Greenhouse Recruiting user information retrieved with the information attributed to the HRIS employee profile.
  3. Reconcile the Greenhouse Recruiting user-profiles and HRIS employee profiles to ensure the correct employee IDs and email addresses are associated with the correct Greenhouse Recruiting users and HRIS employees.
  4. If you're unable to update the necessary info on the Greenhouse Recruiting user(s) to resolve the issue, click here to open a ticket with Greenhouse Support.

Missing required field: email, first/last name, or employee ID

Email subject HRIS Link: User import completed with errors
Error information Server broke connection
Issue

The email address, first name, last name, or employee ID was not provided in the HRIS report for the employee in question. Greenhouse Recruiting requires an email address, employee ID, first name, and last name for each employee in the HRIS report.

Blocking error? No, this is not a blocking error.
Solution
  1. Audit the employee profile in your HRIS to ensure the employee profile has an email address, first name, last name, and employee ID.
  2. If all required fields are filled out in the HRIS, verify the HRIS ISU has access to the employee’s email address, first name, last name, and employee ID.
  3. Wait 15 minutes for the HRIS Link user import report to run again after updating the email address.
  4. If the error persists after updating the employee profile in the HRIS with an email address, click here to open a ticket with Greenhouse Support.

Server broke connection

Email subject HRIS Link: User import completed with errors
Error information Missing required field: email
  or
Missing required field: first_name
  or
Missing required field: last_name
  or
Missing required field: employee_id
Issue This error indicates a rare server issue that may occur with HRIS Link. This error should resolve by itself the next time the import runs.
Blocking error? Yes, this is a blocking error. Updates won't occur in Greenhouse Recruiting until the error is resolved.
Solution If the issue persists, click here to open a ticket with Greenhouse Support. Please include the workflow ID and the error message that occurred.