The Rotaready Updates page is where all events from the integration are displayed. Each event has a status and may include warning or error messages. Understanding what these mean is important; not all warnings are equal.
⚠️Important! Events are classified by severity. CRITICAL alerts appear at the top in red and require immediate action. Events can also be exported to CSV or Excel.
Two different things: status and severity
The status describes what happened to the event. Each event has one. The severity describes what the integration found and attaches to the messages on an event. A single event can carry several messages at different severities.
The important consequence: an event carrying warnings is a successful event. Only failed events can be retried.
Event Status Indicators
Each event on the Rotaready Updates page displays one of the following statuses. The page can be filtered by status using the status filter at the top of the events list, allowing you to focus on specific event types, such as Failed or Successful with Warnings.
Status | Meaning | Action required | Can it be retried? |
Successful | Event processed without issues | None | No |
Successful with Warnings | Event processed, with one or more warnings | Review warnings | No |
Failed | The event did not process | Identify the cause, correct it, then retry | Yes |
Pending | Queued and waiting to process | Wait | No — already queued |
Processing | Currently being processed | Wait | No |
Skipped | The integration determined the event did not need processing | None | No |
Held | The integration determined the event should not proceed yet | None | No |
📌Note: Skipped and Held are not failures. Where several events for a company are handled together, all but the last may show as Skipped, with the last carrying the outcome for the group.
⚠️Important: An event that remains in Processing for an extended period has been interrupted part-way through. It is not a failed event, so it cannot be retried. Raise this with support.
The Difference Between warnings and errors
Errors
⚠️Important: For a rota sign-off, an error stops the pay element import for every employee in it, not just the one named in the message. No pay elements are written, and the pay period keeps those from the last successful import.
An error means the event did not process and the data was not transferred.
Warnings
A warning means the event processed, but something was flagged. Warnings do not always mean something has gone wrong, but some do mean an employee will not be paid correctly.
📌Note: Because a warning sits on an event that completed, there is nothing to retry. Correcting the cause takes effect at the next sign-off or update for that employee.
Warnings that need immediate attention
Rotaready user [NAME] has not been mapped to a Paycircle user. User was skipped.
That employee's shifts and data have not transferred at all, and they will not appear in payroll for this period. Go to the team mapping screen and match or create the employee.
Pay element not found.
⚠️Important: This one causes the import to fail for the whole company, not only for the element or employee named.
A pay element in Rotaready has no matching element in Paycircle. Create the missing element in Paycircle using the name shown in the message, then retry the failed event.
No hourly rate found for user in Rotaready salaries to calculate holiday pay
For salaried employees, this is expected and needs no action. For hourly employees, it needs looking at. Check the rates recorded in Rotaready cover the dates taken.
Holiday element not found in company pack. Please add Holiday element to process holiday from Rotaready.
Your pack has no element matching the text Holiday Pay. No holiday transfers for anyone until it exists, although shifts and sickness still import normally.
Business category mapping missing for the employee's site.
Raised at Critical severity. A Critical blocks the payroll run until it is dismissed, so resolve it before anything else. Map the site on the entity mapping screen.
Errors and what they mean
Failed to connect using the API credentials you entered.
⚠️Important: Do not disconnect and reconnect to resolve this. Disconnecting removes your site selection, every employee link and the salary settings, and switches off your reference period setup.
Work through all three credentials: the realm (case-sensitive), the key and secret (check for transcription errors), and whether the Rotaready environment is active.
An unexpected error occurred whilst processing the event
This covers transient problems such as a timeout or an interrupted connection. It is the one error worth retrying without changing anything first.
The event type is not supported
Retrying will not help. Reach out to our support team for further assistance.
Recommended review approach
Export the events rather than working from the page alone.
Review Critical alerts first — these block the payroll run until dismissed.
Review failed events next — the data has not transferred and must be resolved before payroll is run.
Review successful with warning events, prioritising the types listed under Warnings that need immediate attention.
Check for repeated warnings on the same employee across multiple days.
Ignore Skipped and Held unless something else suggests a problem.