The Complete Update job (PAY355) is a critical process for finalising and updating payroll data. However, there may be instances where this job fails to complete due to various reasons.
We have compiled a list of possible causes for the failure of the PAY355 job and how to resolve these.
Locked job
A user may be logged into a screen, which locks the job.
To resolve this, ask all users to exit the Core screens. If the job has not completed after approximately 10 minutes, please follow the steps outlined below.
PAY355.BAT file
The PAY355.BAT file may not be set up correctly.
To resolve this, retrieve the relevant text files, such as pay355.log.
To do this, check how to retrieve a log file then raise a case online and include a copy of the log file.
PAY300 job failure
The Run Payroll Update (PAY300) job did not complete successfully.
To resolve this, obtain the relevant text files, such as pay300.log and trace files.
To do this, check how to retrieve a log file then raise a case online and include a copy of the log file.
PAY290 job with different dates
The payroll job (PAY290 or PAY140) was run for a single employee with differing processing dates.
To resolve this, retrieve the relevant text files, such as pay355.log.
To do this, check how to retrieve a log file then raise a case online and include a copy of the log file.
Update data issues
After rollback, some tables need to be cleared in the background.
To resolve this, retrieve the relevant text files, such as pay355.log.
To do this, check how to retrieve a log file then raise a case online and include a copy of the log file.
Timing conflicts
The job was run while the system was under maintenance or during a minor version release.
If the job was executed during a PeopleXD minor release, it may fail after several retries and appear stuck in the system. This occurs because the database enters Restricted Mode during maintenance and does not allow user connections.
Please avoid running any jobs during scheduled maintenance or release windows, as this can lead to failures. Jobs can be cleared and re-run in these situations, but only after support has checked the log files and confirmed that this was the cause of the issue.
To resolve this, retrieve the relevant text files, such as pay355.log.
To do this, check how to retrieve a log file then raise a case online and include a copy of the log file.