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. Each error carries a stable code (for example, REVL-EXTN-1001) that you can search for on this page and quote when contacting support.
The Revel integration keeps a deliberately thin error surface: rather than raising its own errors, it passes Revel's own response 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. Because of this, a single code can cover several distinct Revel messages; the resolution for each error below explains the conditions you are most likely to hit and how to correct them.
If a resolution refers to your Managed Integration Service Provider (MiSP), that is the partner who manages your iPaaS.com mappings, connection credentials, and configuration on your behalf; they are your first point of contact when an error cannot be resolved from the steps below.
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.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Connection and Authentication
Employee and Timesheet Transfers
Error Collection
Connection and Authentication
Connection Test Failure
REVL-AUTH-1001 - The connection to Revel 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 and Timesheet Transfers
Revel Rejected the Transfer
REVL-EXTN-1001 - Error calling Revel {action}: {details}
Description: When Revel rejects a record while iPaaS.com is writing an employee or a timesheet, Revel's response is passed through to the error log under this code. The
{action}and{details}shown are taken from Revel's own response. The conditions you are most likely to see are:A required field is missing. Revel requires a first name, last name, PIN, and start date on every employee, and a clock-in time, employee, establishment, and hourly wage on every timesheet entry. The employee PIN and start date are read from the RevelEmployeePIN and RevelEmployeeStartDate custom fields on the iPaaS.com Employee record; the establishment and wage on a timesheet ship as fixed example values that must be replaced during implementation.
The employee PIN is already in use. Revel requires each employee PIN to be unique and no longer than 10 characters, and rejects a transfer that supplies a PIN another employee already has.
The daily API limit has been exceeded. Revel enforces a daily allowance on API calls and rejects further requests until it resets. Revel does not publish the specific number of calls the allowance permits.
Resolution: Match the resolution to the condition in Revel's response:
For a missing employee field, confirm the iPaaS.com Employee has a first name and last name, and that the RevelEmployeePIN and RevelEmployeeStartDate custom fields are present and populated before transferring.
For a missing timesheet field, review the EstablishmentId and RoleWage mappings on the Add/Update Revel Timesheet FROM iPaaS.com collection and replace the shipped example values with ones valid for your Revel account, and confirm the timesheet has a clock-in time. The per-mapping notes on that collection describe each required value.
For a duplicate PIN, assign each employee a unique PIN of 10 characters or fewer in the RevelEmployeePIN custom field, then transfer again.
For an exceeded daily API limit, wait for the allowance to reset and re-run the transfer; to reduce the chance of reaching it, avoid running several large transfers at the same time and stagger high-volume synchronization. If you reach the limit regularly during normal operation, contact your MiSP, or iPaaS.com Support at support@ipaas.com, with the tracking details from the error log.