HRIS Link job import errors – Greenhouse Support

Permissions: —

Product tier: Available to Expert tier subscription 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: Job import failed	No office exists with Name or External ID <value> or No department exists with Name or External ID <value>
HRIS Link: Job import failed	Error message: Custom Field {CUSTOM_JOB_FIELD_NAME} has no option for value '<VALUE>'
HRIS Link: Job import failed	No user exists with Email or Employee ID <value>
HRIS Link: Job import failed	403 Forbidden
HRIS Link: Job import failed	401 Unauthorized
HRIS Link: Job import completed with errors	Hiring Manager with ID <value> can not access job or Recruiter with ID <value> can not access job
HRIS Link: Job import completed with errors	X jobs found in Greenhouse with requisition_id: <value>
HRIS Link: Job import completed with errors	Access denied
HRIS Link: Job import completed with errors	Couldn't find a custom_field in organization using <value>
HRIS Link: Job import completed with errors	Exactly one person must be designated responsible
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	Resource not found
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	Currency unit is required for currency custom fields
HRIS Link: Job import completed with errors	Must be one of [currency units]
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	REQ_ID Partial Recruiter data provided or REQ_ID Partial Hiring Manager data provided
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®️	Error message from Workday®️: 503: Service unavailable
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	{REQ_ID} Server error

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 does not 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: Audit the HRIS Link job import report (or the job in your HRIS) for the office or department name or external ID that caused the error. In Greenhouse Recruiting, go to Configure > Organization. Confirm the office or department name does not exist in Greenhouse Recruiting. To audit the external ID for an office or department in the Greenhouse Recruiting UI, to click the Edit icon next to the office or department name. If you need to audit all external IDs, leverage the Harvest API or reach out to Greenhouse Support. If the office or department name/external ID does not exist in Greenhouse Recruiting and you have office import or department import: Confirm the office exists in your HRIS with the appropriate external ID and name. Wait for office import or department import to run again, then audit to see if this error persists after the office with the correct ID has been created/updated by HRIS Link.

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: Audit the custom option values that are available in the HRIS and copy the exact <VALUE> that's missing from Greenhouse Recruiting. In Greenhouse Recruiting, go to Configure > Custom Options > Click Job to view the list of job custom fields > click to edit the custom field listed in the error message. Audit the available custom options and confirm the option does not exist. If you are not using a Custom Option Sync via Workday®️ RaaS (the picklist can be edited in Greenhouse Recruiting): Add the option value exactly as it appears in the HRIS. Wait 15 minutes for the report to run again If the error persists, click here to open a ticket with Greenhouse Support. If you are using a Custom Option Sync via Workday®️ RaaS (the picklist cannot be edited in Greenhouse Recruiting): Manually refresh the custom option sync by going to Configure > Dev Center > Workday Administration > Sync a Greenhouse custom field with a Workday Report-as-a-service > click the edit icon next to the RaaS custom option sync you wish to refresh Click Refresh report at the top of the page. Go to Configure > Custom Options > Job to view the list of job custom fields > click to edit the custom field listed in the error message. Audit the available custom options and confirm the missing value was added. Wait 15 minutes for the job import report to run again. If the error persists, click here to open a ticket with Greenhouse 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 Greenhouse User account; the HRIS report value must match a 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: In Greenhouse Recruiting, go to Configure > Users > search for the user who was included in the HRIS report (for example, the Recruiter or Hiring Manager). If you cannot find the user, you must create them in Greenhouse Recruiting. If you are able to find the user, click into their profile and verify the Greenhouse Recruiting employee ID and/or email address matches what was included in the HRIS report. If your organization does not have user import: If the value included in the HRIS report does not match the Greenhouse Recruiting user's employee ID or email address, you must update the Greenhouse Recruiting user's profile accordingly. Wait 15 minutes for the report to run again. If the error persists, click here to open a ticket with Greenhouse Support. If your organization has user import: Update the employee ID or email address for the employee in question in your HRIS so it flows to Greenhouse Recruiting on the next run of the report. Wait 15 minutes for user import to run again. 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 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 the resource, despite providing authentication. This may be caused by the ISU credentials expiring, or the On-Behalf-Of User's (named: HRIS Link) permissions are 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: In the HRIS, audit the ISU credentials used to access the job import report. Confirm the ISU credentials are active and have permissions for the Report. Audit the Greenhouse Recruiting user named HRIS Link to ensure the permissions have not changed recently (Configure > Users). Wait 15 minutes for job import to run again. If the error persists, click here to open a ticket with Greenhouse 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: In Greenhouse (Configure > Users), audit the ISU used for the HRIS Link integration (named: HRIS Link). Confirm the ISU is a Site Admin with all user-specific permissions. If the user is not a Site Admin with all user-specific permissions, update the permissions accordingly. Wait 15 minutes for job import to run again. If the error persists, click here to open a ticket with Greenhouse 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 using the employee ID provided in the HRIS report.
Blocking error?	No, this is not a blocking error.
Solution	Take the following steps to troubleshoot this issue: In your HRIS, look up the user associated with the employee ID that is defined for the hiring_managers or recruiters field. In Greenhouse, navigate to Configure > Users > click into the user's profile in question. Confirm the employee ID defined in Workday®️ is the same as it appears in Greenhouse Recruiting. Confirm the Greenhouse Recruiting user in question is active (not deactivated) in Greenhouse Recruiting. If the ID provided matches the employee_ID and the GHR user profile is active in Greenhouse: Audit the HRIS Link Greenhouse ISU (Configure > Users > click into the "HRIS Link" user profile) Ensure the HRIS Link GHR User is a "Site Admin" with all user-specific permissions. If the HRIS Link user profile doesn't have all user-specific permission, update the permissions to be so. Wait 15 minutes for the next job import report to run. If the error persists, click here to open a ticket with Greenhouse Support.

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: In Greenhouse Recruiting, go to All Jobs > search for the requisition ID > click into each of the jobs in question. Audit each job to determine which job should be maintained. Go to the Job Info page of the job that will not be kept. Click the Edit icon next to Status > close the job > click Save > click Delete. Wait 15 minutes for job import to run again. Note: Deleting a job is a permanent action that cannot be undone. If the error persists, click here to open a ticket with Greenhouse Support.

Access denied

Email subject	HRIS Link: Job import completed with errors
Error information	Access denied
Issue	This error occurs when HRIS Link has issues accessing Harvest API via the configured credentials and can not access the job to edit it.
Blocking error?	No, this is not a blocking error.
Solution	Take the following steps to troubleshoot this issue: Audit the following areas: The permissions of the HRIS Link user in your organization's Greenhouse Recruiting account to ensure the user is an active Site Admin User with all user-specific permissions enabled. The job (by requisition ID) in Greenhouse to ensure the job in Greenhouse is not "confidential." The API key used for the HRIS Link integration to ensure the permissions haven't been audited. If you are unable to resolve the issue, click here to open a ticket with Greenhouse Support.

Couldn't find a custom_field in organization using <value>

Email subject	HRIS Link: Job import completed with errors
Error information	Access denied
Issue	This error occurs when HRIS Link has issues accessing Harvest API via the configured credentials.
Blocking error?	No, this is not a blocking error.
Solution	Couldn't find a custom_field in organization using <value>This error means the Job Custom Field defined in the HRIS report column header could not be found in Greenhouse Recruiting.

Exactly one person must be designated responsible

Email subject	HRIS Link: Job import completed with errors
Error information	Exactly one person must be designated responsible.
Issue	This error means there is more than one ID entered for the recruiters field on the job import report. Job import does not support assigning multiple recruiters.
Blocking error?	No, this is not a blocking error.
Solution	Take the following steps to troubleshoot this issue: Audit the HRIS report to see if more than one user is defined in the recruiter field. If more than one user is defined, update the HRIS report so only one primary recruiter is included moving forward. Wait 15 minutes for job import to run again. If the error persists, click here to open a ticket with Greenhouse Support. If only one ID is defined for the recruiters field: Wait 15 minutes for job import to run again. If the error persists, click here to open a ticket with Greenhouse 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: Audit the Calculated Field logic for the HRIS Report and confirm it is up to date and valid. Ensure all IDs defined in the template_job_id logic exist are valid job IDs in Greenhouse. If all the template_job_ids that exist in the HRIS are also in Greenhouse Recruiting, audit the HRIS report for the specific job for which this error was triggered, and confirm the Calculated field for template_job_id defined a job ID. If no job ID was defined, revisit the calculated field logic to determine why. Wait 15 minutes for job import to run again. 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: `https://app.greenhouse.io/sdash/{job ID}` If the error persists, click here to open a ticket with Greenhouse 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: Audit the permissions of the HRIS Link user in your Greenhouse Recruiting account to ensure the user is an active Site Admin with all user-specific permissions enabled. Audit the HRIS Link Harvest API key to ensure it has all required API permissions. Audit the Change Log (Configure > Change Log) to see if anyone has updated HRIS Link Harvest API key permissions or the HRIS Link user. Confirm the job import report still is enabled for Web Services in your HRIS. Confirm the ISU credentials defined for HRIS Link still have access to the job import report in your HRIS. Confirm the number_of_openings defined in the HRIS report is not 0. If all of the above is valid, click here to open a ticket with Greenhouse 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	The job was created in Greenhouse Recruiting, but it is likely certain aspects of the job were not updated/created appropriately.
Blocking error?	No, this is not a blocking error.
Solution	This error should be followed by a second error message calling out 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.

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. See Report specification: Import jobs from Workday®️ for expected format.
Blocking error?	No, this is not a blocking error.
Solution	Take the following steps to troubleshoot this issue: Audit the Currency field data included in the HRIS report to ensure it meets Greenhouse's Report Spec requirements (Unit must come before the amount). Confirm the currency is defined before the amount (that is, <wd:Salary>USD 100,000</wd:Salary> for a currency field, or <wd:Salary_Range>$80,000 - 100,000</wd:Salary_Range2> for a currency range field). If the currency is not defined, or is defined improperly, update the currency field format in the HRIS report to meet the requirements outlined in the following Support Center article: Report specification: Import jobs from Workday®️ Wait 15 minutes to see if the error persists after the next job import run. If the error persists, click here to open a ticket with Greenhouse 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 the report specification documentation: Report specification: Import jobs from Workday®️.
Blocking error?	No, this is not a blocking error.
Solution	Take the following steps to troubleshoot this issue: Audit the Currency field data included in the HRIS report to ensure it includes a valid ISO-4217 currency code. Confirm the currency is defined with the correct spelling (see full list of currency units listed in the error). If the currency is not defined, or is defined improperly, update the currency field format in the HRIS report to meet the requirements outlined in the following Support Center article: Custom Options: Report Specification Wait 15 minutes to see if the error persists after the next job import run. If the error persists, click here to open a ticket with Greenhouse 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: In Greenhouse Recruiting, navigate to Configure > Users > search for the HRIS Link user. Audit the permissions of the HRIS Link user to ensure they are an active Site Admin user with all the user-specific permissions enabled. Audit the Change Log (Configure > Change Log) to see if another user has updated the HRIS Link user's permissions. 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 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 Opening_IDs = P100; P101
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: Audit your organization's HRIS Link job import report. Confirm that both the Recruiters and Recruiter_Role_ID report headers are included. Confirm that both the Hiring_Managers and Hiring_Manager_Role_ID report headers are included. If one of the report headers is missing, reference the Report Specifications and add the missing report header. Wait 15 minutes to see if the error persists after the next job import run. If the error persists, click here to open a ticket with Greenhouse 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: Audit the HRIS Link job import report to verify that name fields which are not blank were applied. The easiest way to accomplish this task is to apply a filter to the HRIS Link job import report. Remove the blank name field. If you do not need the name field, remove it from the report or enter it as null (rather than blank text). If you'd like to further discuss using HRIS Link without applying a name field, click here to open a ticket with Greenhouse 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: Audit the HRIS Link job import report (and your HRIS) to the location applied to the import. Audit your Greenhouse instance to see the external ID for the office that should have been applied via HRIS Link as the `job_post_location`. If the `external_id` of the office in Greenhouse does not match the value provided on the HRIS Link job import report for `job_post_location`, update your HRIS. If the `external_ID` of the office in Greenhouse does match the `job_post_location external_id` that is on the HRIS Link job import report, reach out to Greenhouse support for further assistance. Wait 15 minutes for the HRIS Link to sync. If the error persists, click here to open a ticket with Greenhouse 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: Set your job board to use your organization's offices. Navigate to Configure > Job Boards & Posts > Select Ellipsis beside your job board > and scroll to Manage locations users can select for job posts. Select Organization offices as the location users can select, and click Save.

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: Audit the HRIS job import report to ensure that web services are enabled for the report. Confirm the ISU credentials' access has not changed or expired. After confirming the report is enabled for web services and the ISU has the appropriate level of access to the report, wait 15 minutes for HRIS Link to run once again. If the error persists, click here to open a ticket with Greenhouse 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: Audit the HRIS Link job import report to ensure it meets the required specifications: Setup HRIS Link job import with 'job requisitions' enabled Setup HRIS Link job import without 'job requisitions' enabled Reference any related errors for more details. If the issue persists, click here to open a ticket with Greenhouse 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: Audit the HRIS Link job import report and ensure none of the below scenarios occur: Number_of_openings = 0 Nested column headers (other than “Position” if Requisitions are enabled) Close_reason value is provided, but status = open If none of the above criteria are met, click here to open a ticket with Greenhouse Support.

Additional resources

Note: Greenhouse Recruiting is not sponsored by, affiliated with, or endorsed by Workday®️.