When you update an appointment, career, or continuous service date, the system automatically recalculates absence history. This process is resource-intensive and may result in a timeout or transaction error if any absence-related data is invalid or problematic.
To resolve this, perform the data checks outlined below.
Data checks to perform
Check | Steps |
Does the employee have any non-live sickness absences without an end date? | 1. Open the SelectHR Administrator Tool. 2. Go to Import/Export Data. 3. Click Create an export definition > Select the data to export. 4. Change the database to SelectHR and log in. 5. Paste the SQL below into the Options > Paste SQL from clipboard
6. Replace 7. Click Data.If any results appear, these open-ended absences must be corrected. Set an end date, ideally the same as the start date, to resolve the issue. |
Does the employee have an absence that spans the effective date on the career history record? | 1. Follow steps 1–4 above to access the export tool. 2. Paste the following SQL 4. Click Data.
If any results appear, and the absence is long or open-ended, it may be causing a timeout.
You can delete the absence, make the career change, then recreate the absence, or ask Support to run a SQL script to update the career record. |
Does the employee have a Holiday History record for the same year they started? | Go to Absence > Absence > Holiday History. The employee should have a Holiday Year record that matches their earliest appointment start date (e.g., 1 June 1990 requires a 1990 holiday record).If it’s missing, add the record and retry your update. |
Does the employee have a Holiday History record for the current year? | In Holiday History, confirm the employee has a record for the current holiday year. If not, create one and try your update again. |
Does the start date of the first appointment and career record match the continuous service date? | Go to Employees > Career History and check the earliest start dates for Appointment and Career against the Continuous Service Date.They should match unless the employee is a TUPE transfer or rejoiner. If so, the Continuous Service Date may be intentionally different—do not change it. |
Does the employee have many active pay history records? | If the employee has many active records in Basic Pay History or Other Pay, trying to end the appointment may cause a timeout. This is because the system tries to set an end date for all active records. Manually enter end dates for each Pay History record before ending the appointment. |
If you’ve completed these checks and still encounter issues, or need help with any of the steps, please raise a new case online and reference this article.
Please include:
The employee’s name.
The change you’re attempting.
The exact error message received.