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: Job import failed |
|
|
HRIS Link: Job import failed |
Error message: Custom Field {CUSTOM_JOB_FIELD_NAME} has no option for value '<VALUE>' |
|
HRIS Link: Job import failed |
|
|
HRIS Link: Job import failed |
|
|
HRIS Link: Job import failed |
|
|
HRIS Link: Job import completed with errors |
Hiring Manager with ID <value> cannot access job or Recruiter with ID <value> cannot access job |
|
HRIS Link: Job import completed with errors |
|
|
HRIS Link: Job import completed with errors |
|
|
HRIS Link: Job import completed with errors |
Missing required field: template_job_id or Template hiring plan does not exist |
|
HRIS Link: Job import completed with errors |
|
|
HRIS Link: Job import completed with errors |
Something went wrong and this job is likely partially created in Greenhouse |
|
HRIS Link: Job import completed with errors |
|
|
HRIS Link: Job import completed with errors |
|
|
HRIS Link: Job import completed with errors |
On-Behalf-Of user does not have permission to assign this role for this job |
|
HRIS Link: Job import completed with errors |
Number of opening IDs does not match the defined number of openings |
|
HRIS Link: Job import completed with errors |
|
|
HRIS Link: Job import completed with errors |
{REQ_ID} Is not required, but can not be updated to blank |
|
HRIS Link: Job import completed with errors |
No office exists with Name or External ID 'external_id' |
|
HRIS Link: Job import completed with errors |
Must be a string; Discovered value: <value> |
|
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 |
|
HRIS Link: Job import failed |
No office exists with Name or External ID <value> or No department exists with Name or External ID <value>
| Email subject | HRIS Link: Job import failed |
| Error information | No office exists with Name or External ID <value> or No department exists with Name or External ID <value> |
| Issue | The office referenced in the HRIS report doesn't exist in Greenhouse Recruiting. The report value must exist as an office name or external ID in Greenhouse Recruiting. |
| 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 your organization is using structured offices and departments:
If your organization is using offices for structured job post locations:
If the office or department name / external ID doesn't exist in Greenhouse Recruiting, and you have office import or department import:
|
Error message: Custom Field {CUSTOM_JOB_FIELD_NAME} has no option for value '<VALUE>'
| Email subject | HRIS Link: Job import failed |
| Error information | Error message: Custom Field {CUSTOM_JOB_FIELD_NAME} has no option for value '<VALUE>' |
| Issue | This error message means the custom field option value referenced in the report "<VALUE>" does not exist as a picklist option for the job custom field in Greenhouse Recruiting. |
| 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 you aren't using a custom options sync via Workday®️ RaaS and the select list can be edited in Greenhouse Recruiting:
If you are using a custom option sync via Workday®️ RaaS and the select list can't be edited in Greenhouse Recruiting:
If the error persists, click here to open a ticket with Greenhouse Technical Support. |
No user exists with Email or Employee ID <value>
| Email subject | HRIS Link: Job import failed |
| Error information | No user exists with Email or Employee ID <value> |
| Issue |
The email address or employee ID referenced in the HRIS report is not associated with an existing, active Greenhouse Recruiting user account. The HRIS report value must match an active Greenhouse Recruiting user's employee ID or email address. |
| 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 your organization does not have user import:
If the error persists, click here to open a ticket with Greenhouse Technical Support. If your organization has user import:
If the job import error persists after user import has updated the user profile in Greenhouse Recruiting, click here to open a ticket with Greenhouse Technical Support. |
403 Forbidden
| Email subject | HRIS Link: Job import failed |
| Error information | 403 Forbidden |
| Issue | A 403 error is returned when the client is not permitted access to a resource, despite providing authentication. This might be caused by an ISU's credentials expiring, or the on-behalf-of user's (named: HRIS Link) permissions not being insufficient. |
| 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. |
401 Unauthorized
| Email subject | HRIS Link: Job import failed |
| Error information | 401 Unauthorized |
| Issue | The 401 Unauthorized error indicates that the request lacks valid authentication credentials for the target resource. For instance, this could be encountered because the integration ISU is not permissioned correctly. |
| 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. |
Hiring Manager with ID <value> can not access job or Recruiter with ID <value> can not access job
| Email subject | HRIS Link: Job import completed with errors |
| Error information |
Hiring Manager with ID <value> can not access job. or Recruiter with ID <value> can not access job. |
| Issue | The hiring manager or recruiter cannot access the job in question because their Greenhouse Recruiting user profile is deactivated or cannot be found. |
| Blocking error? |
No, this is not a blocking error. |
| Solution |
Take the following steps to troubleshoot this issue:
|
X jobs found in Greenhouse with requisition_id: <value>
| Email subject | HRIS Link: Job import completed with errors |
| Error information | X jobs found in Greenhouse with requisition_id: <value> |
| Issue | This error message means there are two jobs in the Greenhouse Recruiting instance with a matching job requisition ID. As a result, job import cannot update the job because job import does not know which of the two existing jobs to update. |
| Blocking error? |
No, this is not a blocking error. |
| Solution |
Someone within your organization must remove one of the two duplicate jobs so only one job exists with the given requisition ID. Below are some steps you can take to resolve this error:
Note: Deleting a job is a permanent action that cannot be undone. If the error persists, click here to open a ticket with Greenhouse Technical Support. |
Access denied
| Email subject | HRIS Link: Job import completed with errors |
| Error information | Access denied |
| Issue |
The issue occurs when the Greenhouse Recruiting integration system user (ISU) for HRIS Link can't grant another a user access to the Greenhouse Recruiting job that it's attempting to update or create. This could be due to the ISU's permissions, a hiring team's user's deactivated status, or the ISU attempting to grant permissions to itself. |
| Blocking error? |
No, this is not a blocking error. |
| Solution |
Take the following steps to troubleshoot this issue:
If you are unable to resolve the issue, click here to open a ticket with Greenhouse Technical Support. |
Missing required field: template_job_id or Template hiring plan does not exist
| Email subject | HRIS Link: Job import completed with errors |
| Error information |
Missing required field: template_job_id or Template hiring plan does not exist. |
| Issue |
This message typically means the required template_job_id field is missing or includes a Job ID that is not valid in Greenhouse Recruiting. This error prevents a job from being created in Greenhouse Recruiting. or This error goes hand in hand with the Missing required field: template_job_id error. This error occurs when the template job ID is not valid. This error prevents a job from being created in Greenhouse Recruiting. |
| Blocking error? |
No, this is not a blocking error. |
| Solution |
Take the following steps to troubleshoot this issue:
Note: You can export the all jobs summary report, which includes the Greenhouse Recruiting job ID for each job. If you prefer to audit an individual template job ID manually, append the job ID to the following URL: If the error persists, click here to open a ticket with Greenhouse Technical Support. |
Resource not found
| Email subject | HRIS Link: Job import completed with errors |
| Error information | Resource not found |
| Issue | This error may be caused by an issue with the On-Behalf-Of User's (named: HRIS Link) permissions, HRIS Link Harvest API key permissions, access to the HRIS Report URL, or the number_of_openings being set to be 0. |
| Blocking error? |
No, this is not a blocking error. |
| Solution |
Take the following steps to troubleshoot this issue:
If all of the above is valid, wait 15 minutes for the process to re-attempt to create or update the job. If the same error occurs on a subsequent attempt, click here to open a ticket with Greenhouse Technical Support. |
Something went wrong and this job is likely partially created in Greenhouse
| Email subject | HRIS Link: Job import completed with errors |
| Error information | Something went wrong and this job is likely partially created in Greenhouse |
| Issue | If you're encountering this error, you should update your HRIS Link Harvest API key to ensure the Jobs > DELETE: Delete job permission is enabled. With this permission, HRIS Link will never partially create a job. With this error, the job was partially created in Greenhouse Recruiting, but it's likely that certain aspects of the job weren't created or updated properly due to another HRIS Link error. |
| Blocking error? |
No, this is not a blocking error. |
| Solution |
This error should be followed by a second error message that describes the issue that caused the partial job creation. For example: R123 Something went wrong and this job is likely partially created in Greenhouse; On-Behalf-Of user does not have permission to assign this role for this job.
Follow the troubleshooting steps provided in the second error message. To permanently resolve this behavior and re-establish HRIS Link's ability to delete jobs, update your HRIS Link Harvest API key to include Jobs > DELETE: Delete job. |
Currency unit is required for currency custom fields
| Email subject | HRIS Link: Job import completed with errors |
| Error information | Currency unit is required for currency custom fields |
| Issue | This error occurs if a currency custom field is missing the currency unit in the HRIS Report. Check out Set up HRIS Link job import with job requisitions enabled for the expected format. |
| Blocking error? |
No, this is not a blocking error. |
| Solution |
Take the following steps to troubleshoot this issue:
If the error persists, click here to open a ticket with Greenhouse Technical Support. |
Must be one of [list of currencies]
| Email subject | HRIS Link: Job import completed with errors |
| Error information | Must be one of: USD, EUR, GBP, ADF, ADP, AED, AFA, AFN, ALL, AMD, ANG, AOA, AON, AOR, ARA, ARL, ARP, ARS, ATS, AUD, AWG, AZM, AZN, BAM, BBD, BDT, BEF, BGL, BGN, BHD, BIF, BMD, BND, BOB, BOP, BOV, BRB, BRC, BRE, BRL, BRN, BRR, BRZ, BSD, BTN, BWP, BYR, BZD, CAD, CDF, CHE, CHF, CHW, CLE, CLF, CLP, CNY, COP, COU, CRC, CSD, CSK, CUC, CUP, CVE, CYP, CZK, DDM, DEM, DJF, DKK, DOP, DZD, ECS, ECV, EEK, EGP, ERN, ESA, ESB, ESP, ETB, FIM, FJD, FKP, FRF, GEL, GGP, GHS, GIP, GMD, GNE, GNF, GQE, GRD, GTQ, GWP, GYD, HKD, HNL, HRK, HTG, HUF, IDR, IEP, ILP, ILR, ILS, IMP, INR, IQD, IRR, ISJ, ISK, ITL, JEP, JMD, JOD, JPY, KES, KGS, KHR, KMF, KPW, KRW, KWD, KYD, KZT, LAJ, LAK, LBP, LKR, LRD, LSL, LTL, LUF, LVL, LYD, MAD, MAF, MCF, MDL, MGA, MGF, MKD, MKN, MLF, MMK, MNT, MOP, MRO, MTL, MUR, MVQ, MVR, MWK, MXN, MXP, MXV, MYR, MZM, MZN, NAD, NFD, NGN, NIO, NLG, NOK, NPR, NZD, OMR, PAB, PEH, PEI, PEN, PGK, PHP, PKR, PLN, PLZ, PRB, PTE, PTP, PYG, QAR, ROL, RON, RSD, RUB, RUR, RWF, SAR, SBD, SCR, SDD, SDG, SDP, SEK, SGD, SHP, SIT, SKK, SLL, SML, SOS, SRD, SRG, SSP, STD, SUR, SVC, SYP, SZL, THB, TJR, TJS, TMM, TMT, TND, TOP, TPE, TRY, TTD, TVD, TWD, TZS, UAH, UAK, UGS, UGX, USN, USS, UYI, UYN, UYU, UZS, VAL, VEB, VEF, VND, VUV, WST, XAF, XAG, XAU, XBA, XBB, XBC, XBD, XCD, XDR, XEU, XFO, XFU, XOF, XPD, XPF, XPT, XTS, XXX, YDD, YER, YUD, YUG, YUM, YUN, YUO, YUR, ZAL, ZAR, ZMK, ZMW, ZRN, ZRZ, ZWC, ZWD, ZWL, ZWN, ZWR |
| Issue | Similar to the other currency field error, this error occurs if the currency unit provided is not a valid ISO-4217 currency code. The full list of supported values is included in the error, as well as in Set up HRIS Link job import with job requisitions enabled. |
| Blocking error? |
No, this is not a blocking error. |
| Solution |
Take the following steps to troubleshoot this issue:
If the error persists, click here to open a ticket with Greenhouse Technical Support. |
On-Behalf-Of user does not have permission to assign this role for this job
| Email subject | HRIS Link: Job import completed with errors |
| Error information | On-Behalf-Of user does not have permission to assign this role for this job. |
| Issue | The HRIS Link user does not have the appropriate permissions to update the job in question. The Greenhouse HRIS Link user should be an active Site Admin with all user-specific permissions granted. |
| Blocking error? |
No, this is not a blocking error. |
| Solution |
Take the following steps to troubleshoot this issue:
If the HRIS Link user is a Site Admin with all the user-specific permissions and no edit to the HRIS User has occurred, click here to open a ticket with Greenhouse Technical Support. |
Number of opening IDs does not match the defined number of openings
| Email subject | HRIS Link: Job import completed with errors |
| Error information | Number of opening IDs does not match the defined number of openings. |
| Issue |
The value in the “Number_Of_Openings” column in the HRIS report does not match the number of Opening IDs listed. For example: Number_Of_Openings = 3 |
| Blocking error? |
No, this is not a blocking error. |
| Solution | Review the requisition in your HRIS and determine why the number of openings specified does not match the count of opening IDs provided. This error will continue until the data is reconciled in your HRIS. |
REQ_ID Partial Recruiter data provided or REQ_ID Partial Hiring Manager data provided
| Email subject | HRIS Link: Job import completed with errors |
| Error information |
REQ_ID Partial Recruiter data provided
or
REQ_ID Partial Hiring Manager data provided
|
| Issue |
The "Recruiters" or "Recruiter Role ID" is missing on the HRIS Link job import report (both are required to assign recruiters to the Greenhouse Recruiting job's hiring team). or The "Hiring Managers" or "Hiring Manager Role ID" column is missing on the HRIS Link job import report (both are required to assign hiring managers to the Greenhouse Recruiting job's hiring team). |
| Blocking error? |
No, this is not a blocking error. |
| Solution |
Take the following steps to troubleshoot this issue:
If the error persists, click here to open a ticket with Greenhouse Technical Support. |
{REQ_ID} Is not required, but can not be updated to blank
| Email subject | HRIS Link: Job import completed with errors |
| Error information |
{REQ_ID} Is not required, but can not be updated to blank. |
| Issue | A blank name field was included in the report results. |
| Blocking error? |
No, this is not a blocking error. |
| Solution |
Take the following steps to troubleshoot this issue:
If you'd like to further discuss using HRIS Link without applying a name field, click here to open a ticket with Greenhouse Technical Support. |
No office exists with Name or External ID 'external_id'
| Email subject | HRIS Link: Job import completed with errors |
| Error information |
No office exists with Name or External ID 'external_id' |
| Issue | The external_id that is applied for the report header of job_post_location does not match an external_id that exists on an office in Greenhouse Recruiting. |
| Blocking error? |
No, this is not a blocking error. |
| Solution |
Take the following steps to troubleshoot this issue:
If the error persists, click here to open a ticket with Greenhouse Technical Support. |
Must be a string; Discovered value: <value>
| Email subject | HRIS Link: Job import completed with errors |
| Error information |
Must be a string; Discovered value: <value> |
| Issue | HRIS Link is attempting to assign a job_post_location within the report, but in order to do so, your job board must be configured to use your organization's offices, and not free-text entries. |
| Blocking error? |
No, this is not a blocking error. |
| Solution |
Take the following steps to troubleshoot this issue:
|
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 job 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 job 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 job 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 job 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 > Dev Center > Workday Administration > Enter credentials to access Workday Tenants or reports. Ensure the username and password match valid Workday®️ credentials. |
{REQ_ID} Server error
| Email subject | HRIS Link: Job import failed |
| Error information |
{REQ_ID} Server error |
| Issue |
Server errors with HRIS Link could mean a variety of items are causing issues with the integration's job import. See the below steps for troubleshooting Server Errors with HRIS Link. |
| 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 none of the above criteria are met, click here to open a ticket with Greenhouse Technical Support. |
Note: Greenhouse Recruiting is not sponsored by, affiliated with, or endorsed by Workday®️.