Overview
This article catalogues the error messages the UKG Ready integration can produce, grouped by the transfer flow that raises them. Each entry gives the message as it appears, what causes it, and what to do about it.
Errors appear in Dashboard / Integration Monitoring / Error Logs.
Not every problem produces an error. Timesheets for an employee who has not yet been transferred to UKG Ready are skipped deliberately and silently — no record is written and nothing is logged. That behaviour is described in the UKG Ready Integration Known Limitations article and in the mapping documentation for the timesheet flow, not here.
Supported Flows
Add/Update UKG Ready Employee TO iPaaS.com
Add/Update UKG Ready Timesheet FROM iPaaS.com
Add/Update UKG Ready Employee TO iPaaS.com
The sign-in and connection errors in this section apply to every transfer the integration makes, including the timesheet flow.
Sign-In Failed
Failed attempting to login to the UKG Ready site ({details from UKG Ready})
Description: UKG Ready rejected the sign-in attempt. The details in brackets are UKG Ready's own response. This happens when the API User, API Password, API Key, or Company ID on the subscription is wrong or has changed, when the service account has been disabled or locked in UKG Ready, or when the account has lost the Web Services permission that allows it to sign in.
Resolution: Confirm the service account is still active in UKG Ready and that its Web Services permissions are intact. Then re-enter the API User, API Password, API Key, and Company ID on the subscription and apply the change. Remember that the Company ID and the API Key are different values in different fields. If the credentials are correct and sign-in still fails, contact iPaaS.com Support at support@ipaas.com.
Cannot Reach UKG Ready
Unable to connect to UKG Ready: {details}
Description: The integration could not establish a connection to the UKG Ready environment at all — as distinct from connecting and being refused. The usual causes are an incorrect API Url on the subscription, a UKG Ready environment that is unavailable or in maintenance, or network filtering between iPaaS.com and UKG Ready.
Resolution: Check that the API Url on the subscription matches the environment you intend to reach, and that the environment is reachable. If UKG Ready is available and the address is correct, contact iPaaS.com Support at support@ipaas.com.
UKG Ready Rejected the Request
Error calling UKG Ready {operation}: {details from UKG Ready} (Http Code: {code})
Description: The integration reached UKG Ready and made a call, and UKG Ready refused it. The operation names the call that failed and the details are UKG Ready's own response. Common causes are a service account that can sign in but lacks permission for the specific data being requested, a record that no longer exists in UKG Ready, or a value UKG Ready will not accept.
Resolution: Read the details in the message — UKG Ready states the reason. If it indicates a permission problem, confirm the service account's Web Services permissions cover the data being transferred. If it indicates the record was not found, confirm the record still exists in UKG Ready. If the reason is unclear or the call should have succeeded, contact iPaaS.com Support at support@ipaas.com with the message and the time it occurred.
Invalid Employee Identifier
The Employee identifier supplied for this transfer is not valid: {value}
Description: The employee identifier supplied for the transfer is not a whole number. It occurs almost always on a Manual Sync where the entered value has extra characters, spacing, or a prefix. The transfer stops before any call is made to UKG Ready.
Resolution: Re-enter the employee's numeric identifier from UKG Ready on its own, with no prefix, suffix, or separator — for example 12345.
Ambiguous Employee Lookup
More than one employee matches the requested external ID prefix
Description: A mapping used the conversion function that finds a UKG Ready employee from the beginning of an external identifier, and more than one employee matched. The function returns a single employee or nothing, so an ambiguous match stops the transfer rather than guessing.
Resolution: Confirm that external identifiers are unique across the employees in scope in UKG Ready, or supply a longer prefix in the mapping so the match resolves to one employee. If the identifiers appear unique in UKG Ready and the error persists, contact iPaaS.com Support at support@ipaas.com.
Add/Update UKG Ready Timesheet FROM iPaaS.com
The sign-in and connection errors described under the employee flow above apply to this flow as well.
Employee Not Linked
Employee Account Id is required but was not supplied
Description: The transfer reached the point of writing to UKG Ready without a UKG Ready employee account identifier. In normal operation the mapping filter prevents this by skipping timesheets whose employee has not been linked, so seeing this error means the link was lost between the filter check and the write — most often because the employee's external-ID link was removed while the transfer was in flight.
Resolution: Confirm the employee has been transferred through Add/Update UKG Ready Employee TO iPaaS.com and is still linked, then re-send the timesheet.
Time Entries Rejected
There were errors saving your time entries: {code} {message from UKG Ready}
Description: UKG Ready accepted the request but refused one or more of the time entries in it, and reported the reason for each. This endpoint reports entry-level problems inside its response rather than failing the whole call, so the integration reads that response and raises what it finds. Common causes are an entry whose date falls outside the period the timesheet declares, a start or end time UKG Ready will not accept, or an entry type that does not exist in the subscriber's UKG Ready configuration.
Resolution: Read the message — UKG Ready names what it objected to and the code identifies the entry. Correct the affected entry on the iPaaS.com timesheet and re-send it. If several entries fail with the same reason, check whether the timesheet's period covers all the days its entries fall on.
Invalid Timesheet Identifier
The Timesheet identifier supplied for this transfer is not valid (problem with the {part}): {value}
Description: The timesheet identifier supplied for the transfer is not in the form this collection expects. The identifier has four parts — the UKG Ready employee identifier, the period start date, the period end date, and a system-generated reference — joined by pipe characters. The message names which part could not be read, or omits that detail when the identifier has the wrong number of parts altogether. It occurs on a Manual Sync where the value is incomplete or hand-composed.
Resolution: This collection is not intended to be driven by Manual Sync, because the fourth part of the identifier is generated by iPaaS.com and cannot be composed by hand. Use the outbound triggers under Outbound Data Flows to move timesheets instead. If you are re-sending a timesheet that has already transferred once, take the identifier from that earlier transfer rather than assembling it.
Batch Transfer Failed
Received an exception during the batch run of {operation}. {first error}
Description: The integration groups its calls into batches, and one of the calls in a batch failed. The message names the operation and reports the first error encountered in that batch. The underlying cause is whatever the reported error describes — most often one of the sign-in, connection, or rejection errors above.
Resolution: Resolve the error reported in the message using the relevant entry above, then re-send the affected records. If the reported error is not one of those described here, contact iPaaS.com Support at support@ipaas.com with the full message and the time it occurred.