Skip to main content

Common AIS error messages and resolutions

Emailed error messages from the HR to APP integration via AIS.

H
Written by Harry Ledger
Updated over 2 months ago

Below is a list of common errors encountered during the integration between SelectHR and PeoplePlanner, along with steps to resolve them.

If your error is not listed here, please raise a new case online and reference the title of this article.

Error

Fix

Employee termination reason is required when Termination date is provided.

If Termination Date in the error email is null:
- Disable integration in PeoplePlanner.
- In PeoplePlanner, go to Employee > Employee > Find, open the employee record.
- Go to Payroll tab, clear the Payroll Number (also called External ID), and Save.
- Wait for the employee record to sync back from SelectHR.
- Once synced, re-enter the Payroll ID and Save.
- Re-enable the integration.

If Termination Date is not null:
- Log into SelectHR > Employees > Career History > Employee > All Appointments and check the end date.
- If most recent appointment has an end date:
- Disable integration in PeoplePlanner.
- Manually terminate employee with termination details (use earliest date after last shift if applicable).
- Save and re-enable integration.
- If most recent appointment doesn’t have an end date:
- Disable integration.
- Clear Payroll Number in PeoplePlanner.
- Save and wait for sync.
- Re-enter Payroll Number and save.
- Re-enable integration.

Unexpected character encountered while parsing value: <. Path '', line 0, position 0

This error is rare and usually does not require action.

Stage 'PushData: Push data to destination' for workflow 'PP to SelectHR' aborted due to timeout

- Restart the AIS Relay Service via Windows Services (services.msc).
- Monitor for further relay errors.
- If repeated, raise a support case.

Termination date cannot be after x

- Disable integration in PeoplePlanner.
- Manually terminate employee with termination date as earliest after last shift.
- Save and re-enable integration.

Failed to push employee due to BadRequest: Incorrect value for lookup data (Field = Employee Type, Value = I)

- If it looks like a typo, map the new value to an existing PeoplePlanner value:
- On-premise: Open AIS Configurator on the AIS Web Server.
- Go to Mappings > Value Mapping for the lookup field.
- Add new record mapping the new value (source) to the correct existing value (target).
- Save changes.
- If hosted, raise a support case.

Error: An item with the same key has already been added.

Possible causes:
- Rostering Link:
- In SelectHR > Admin > Accounts and Rostering > Rostering Links, open PP Rostering Link > Link Employees.
- Remove any expiry dates and save.
- Holiday Record:
- In SelectHR > Absence > Holiday History, add a holiday record for current year if missing, using a template.

Failed to push employee: No employee with EmployeeID 'X' found with an active link.

Possible causes:
- Employee should not have been removed from rostering link:
- Add employee back via SelectHR > Admin > Rostering Links > PP Rostering Link > Link Employees.
- Record not needed in PeoplePlanner:
- Disable integration.
- Manually terminate employee.
- Save and re-enable integration.
- Employee needed in PeoplePlanner but no HR link required:
- Disable integration.
- Clear Payroll Number in PeoplePlanner.
- Save and re-enable integration.

Failed to push employee due to: Error when terminating existing employee SPOutputType - Exception

- Check employee’s Career History in SelectHR.
- If most recent appointment has an end date:
- Disable integration.
- Manually terminate employee.
- Save and re-enable integration.
- If no end date:
- Remove and re-add employee in Rostering Links in SelectHR.

Failed to push Training 'Unknown' due to BadRequest

- Occurs when Training & Qualification in HR do not match those in PeoplePlanner.
- Create the training and qualification in PeoplePlanner to match HR naming conventions.


If you need further assistance or your issue is not resolved by the above, please raise a support case referencing this article title and include detailed information about the error and affected records.

Did this answer your question?