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.
HRIS Link errors serve to inform you of the cause of the problem and the suggested solution.
Check out the table below to find the error name from your email, along with details on how to solve it.
Note: Some errors are blocking errors, meaning updates to information in Greenhouse Recruiting are blocked by the error. You need to resolve the error in order for HRIS Link to sync properly.
Email subject | Error name |
HRIS Link: Office / department import completed with errors |
Creation failed: Validation failed: Name has already been taken |
HRIS Link: Office / department import completed with errors |
|
HRIS Link: Office / department import completed with errors |
We found an invalid hierarchy related to the following departments: {external_id} |
HRIS Link: Office / department import completed with errors |
Child with invalid Parent (Test009) The parent department was not found. |
HRIS Link: Failed to access Workday®️ |
We encountered an error when trying to poll your Workday®️ report |
HRIS Link: Failed to access Workday®️ |
Error message from Workday®️: 500: Processing error occurred |
HRIS Link: Failed to access Workday®️ |
|
HRIS Link: Failed to access Workday®️ |
Error message from Workday®️: 400: Validation error occurred |
HRIS Link: Failed to access Workday®️ |
Error message from Workday®️: 401: Invalid username or password |
Creation failed: Validation failed: Name has already been taken
Email subject | HRIS Link: Office / department import completed with errors |
Error information | Creation failed: Validation failed: Name has already been taken |
Issue |
This error message occurs when HRIS Link attempts to create a new office or department in Greenhouse Recruiting, but the office or department name included in the HRIS Report matches an existing office or department in Greenhouse Recruiting. |
Blocking error? | No, this is not a blocking error. |
Solution |
|
Resource not found
Email subject | HRIS Link: Office / department import completed with errors |
Error information | Resource not found |
Issue |
This error occurs when there are issues with the "on-behalf-of" user permissions, HRIS Link Harvest API key permissions, or access to the HRIS Report URL. |
Blocking error? | No, this is not a blocking error. |
Solution |
|
We found an invalid hierarchy related to the following departments: {external_id}
Email subject | HRIS Link: Office / department import completed with errors |
Error information | We found an invalid hierarchy related to the following departments: {external_id} |
Issue |
This HRIS Link error is a blocking error, all departments will not be processed until the invalid hierarchy is fixed. Typically, this error occurs because of the following circumstances:
|
Blocking error? | Yes, this is a blocking error. Updates in Greenhouse Recruiting won't occur until the error is resolved. |
Solution |
|
Child with invalid Parent (Test009) The parent department was not found.
Email subject | HRIS Link: Office / department import completed with errors |
Error information | Child with invalid Parent (Test009) The parent department was not found. |
Issue |
This child department is referencing an external_parent_id that does not exist. |
Blocking error? | No, this is not a blocking error. Departments or offices with an invalid external_parent_id will not be added, but any valid departments or offices on the HRIS Link report will be added. |
Solution |
|
We encountered an error when trying to poll your Workday®️ report
Email subject | HRIS Link: Failed to access Workday®️ |
Error information |
We encountered an error when trying to poll your Workday®️ report at . . . |
Issue | This error is typically an issue related to the HRIS report URL (for example, if something has changed with the ISU's access to the report URL). |
Blocking error? |
Yes, this is a blocking error. Updates will not occur in Greenhouse Recruiting until the error is resolved. |
Solution |
Take the following steps to troubleshoot this issue:
If the error persists, click here to open a ticket with Greenhouse Technical Support. |
Error message from Workday®️: 500: Processing error occurred
Email subject | HRIS Link: Failed to access Workday®️ |
Error information |
Error message from Workday®️: 500: Processing error occurred |
Issue | This error typically indicates a formatting or filtering error within your HRIS Link import report, and typically comes alongside a more detailed error. |
Blocking error? |
Yes, this is a blocking error. Updates will not occur in Greenhouse Recruiting until the error is resolved. |
Solution |
Take the following steps to troubleshoot this issue:
Reference any related errors for more details. If the issue persists, click here to open a ticket with Greenhouse Technical Support. |
Error message from Workday®️: 503: Service unavailable
Email subject | HRIS Link: Failed to access Workday®️ |
Error information |
Error message from Workday®️: 503: Service unavailable |
Issue | This error typically indicates that Workday®️ is down for maintenance and HRIS Link cannot access your import report. |
Blocking error? |
Yes, this is a blocking error. Updates will not occur in Greenhouse Recruiting until the error is resolved. |
Solution |
This error typically resolves once Workday®️ maintenance is complete. |
Error message from Workday®️: 400: Validation error occurred
Email subject | HRIS Link: Failed to access Workday®️ |
Error information |
Error message from Workday®️: 400: Validation error occurred |
Issue | This error indicates the import report could not be accessed. |
Blocking error? |
Yes, this is a blocking error. Updates will not occur in Greenhouse Recruiting until the error is resolved. |
Solution |
This error indicates a security issue on the import report that must be resolved in Workday®️. |
Error message from Workday®️: 401: Invalid username or password
Email subject | HRIS Link: Failed to access Workday®️ |
Error information |
Error message from Workday®️: 401: Invalid username or password |
Issue | This error indicates invalid Workday®️ credentials in Greenhouse Recruiting. |
Blocking error? |
Yes, this is a blocking error. Updates will not occur in Greenhouse Recruiting until the error is resolved. |
Solution |
Navigate to Configure > DevCenter > Workday®️Administration > Enter credentials to access Workday®️ Tenants or reports. Ensure the username and password match valid Workday®️ credentials. |
Note: Greenhouse Recruiting is not sponsored by, affiliated with, or endorsed by Workday®️.