Overview
This article catalogs the errors you may encounter while synchronizing employee and timesheet data between iPaaS.com and Revel, and how to resolve each one. Errors appear in Dashboard / Integration Monitoring / Error Logs.
Most errors in this integration originate in Revel and are passed through to the iPaaS.com error log — for example, a record that fails Revel's validation, or a request that exceeds Revel's daily call allowance. The entries below group these by the flow in which you are most likely to see them.
Some conditions are handled without producing an error and so do not appear here. In particular, a timesheet whose employee has not yet been transferred to Revel is skipped silently rather than reported as an error; that behavior is described in the Add/Update Revel Timesheet TO iPaaS.com mapping collection and in the Revel Integration Known Limitations article.
Supported Flows
Connection and Authentication
Employee Transfers
Timesheet Transfers
API Rate Limits
Connection and Authentication
Connection Test Failure
The connection could not be established. Revel returned an authentication or address error.
Description: iPaaS.com verifies your credentials by retrieving your Revel company record. When the API Key, API Secret, or API Url is wrong — or the key and secret have not been enabled for REST API access by Revel — Revel rejects the request and its response is shown in the error log.
Resolution: Confirm the API Url is your own Revel address in the form https://yoursubdomain.revelup.com, and that the API Key and API Secret match the values Revel provided. If the values are correct and the connection still fails, confirm with Revel that REST API access has been enabled for your account. See the Revel Connections and Settings article for where each value is entered.
Employee Transfers
These errors can occur when writing an employee into Revel through the Add/Update Revel Employee FROM iPaaS.com collection.
Missing Required Employee Field
Revel rejected the employee because a required field was missing.
Description: Revel requires a first name, last name, PIN, and start date on every employee it creates. The PIN and start date are read from the RevelEmployeePIN and RevelEmployeeStartDate custom fields on the iPaaS.com Employee record. When one of these values is empty, Revel returns a validation error and the employee is not created.
Resolution: Confirm that the iPaaS.com Employee has a first name, a last name, and both custom fields populated before transferring. Add the RevelEmployeePIN and RevelEmployeeStartDate custom fields to your iPaaS.com Employee records if they are not already present, and populate them for every employee you send to Revel.
Duplicate Employee PIN
Revel rejected the employee because the PIN is already in use.
Description: Revel requires each employee PIN to be unique and returns a validation error when a transfer supplies a PIN that another employee already has. The PIN also cannot exceed 10 characters.
Resolution: Assign each employee a unique PIN of 10 characters or fewer in the RevelEmployeePIN custom field, then transfer again. If you are unsure which employee already holds a PIN, check your employee list in Revel.
Timesheet Transfers
These errors can occur when writing a timesheet into Revel through the Add/Update Revel Timesheet FROM iPaaS.com collection.
Missing Required Timesheet Field
Revel rejected the timesheet because a required field was missing.
Description: Revel requires a clock-in time, an employee, an establishment, and an hourly wage on every timesheet entry it creates. The establishment and wage ship as fixed example values that must be replaced during implementation. When one of these values is missing or invalid, Revel returns a validation error and the timesheet is not created.
Resolution: Review the EstablishmentId and RoleWage mappings on the Add/Update Revel Timesheet FROM iPaaS.com collection and replace the shipped example values with ones that are valid for your Revel account. Confirm the timesheet has a clock-in time before transferring. The per-mapping notes on that collection describe each required value.
Employee Not Linked in Revel
Revel rejected the timesheet because its employee could not be found.
Description: A timesheet must be attached to an employee that already exists in Revel and has been linked by a prior transfer. When no linked Revel employee exists for the timesheet's employee, Revel rejects the record because the employee is required.
Resolution: Transfer the employee through the Add/Update Revel Employee FROM iPaaS.com collection first, confirm it succeeded, then transfer the timesheet again.
API Rate Limits
Daily API Limit Exceeded
You have exceeded your daily API limit.
Description: Revel enforces a daily allowance on the number of API calls an account may make. When that allowance is exhausted, Revel rejects further requests until it resets. Revel does not publish the specific number of calls the allowance permits.
Resolution: Wait for the allowance to reset, then re-run the transfer. To reduce the chance of reaching the limit, avoid running several large transfers at the same time and stagger high-volume synchronization. If you reach the limit regularly during normal operation, contact iPaaS.com Support at support@ipaas.com.