Skip to main content
Background

Where to find this section

Updated over a week ago

Navigation

You can locate this section in the left sidebar.

iPaaS.com is in a Unique Position to Help with Data

Because iPaaS.com has all data flowing either TO or FROM the platform, it is able to show logs for all of those transactions.

  • By reviewing the activity logs and events queue, you have a 360 degree view of where data is going to and from.

  • By utilizing error logs, you can see any errors in data transmission.

  • If you end up with records that are not matched you can use the show unmatched feature to diagnose this issue and reset external IDs.

  • Should you need to repopulate a data source you can use the manual sync functionality.

  • If anything is deleted accidentally you can leverage the reactivate data tool.

Errors

When an API call fails (and therefore the record is not transmitted) it logs an error and those are visible in iPaaS.com. Calls can fail for a variety of reasons, including, but not limited to:

  • The API credentials are inaccurate or have had their permissions changed/revoked.

  • A field is only configured to accept data in a certain format (i.e. a date in the format of 2023-08-09) and the API call is feeding it data in another (i.e. August 9, 2023).

  • The API is being throttled by a certain system.

  • A corresponding dependent record is not created (i.e. trying to create an address for a customer, but the customer does not yet exist).

iPaaS.com logs errors from both incoming and outgoing calls.

Gracefully Retry

  • When an API call fails, iPaaS.com will automatically retry that call to see if it can get it to complete, but the frequency at which it does will diminish over time according to the following schedule:

    • 10 * attempt * (attempt + 1)

    • This means the first attempt is treated as a 0 and sent immediately, then 20 minutes, then 60 minutes, etc.

  • At any time a user is able to go into the error logs and retry a specific error.

Deleted Records

  • In iPaaS.com all deleted records are kept for a certain amount of time as deactivated records.

  • In this window, a user can reactivate those records.

  • If a record is deactivated in iPaaS.com external systems will treat it as deleted, but actions taken on those records are dependent on the configuration of webhooks and mappings.

Did this answer your question?