How long does it take to set up Tarsal?

It depends on your source and destination. Configuration is as easy as filling out a form, and the leg work simply comes down to gathering the appropriate prerequisites for setup. This may include authentication information, ARNs or Database connection information. You can view the prerequisites in our Sources and Destinations pages.

Do you store my data?

Date is transiently stored in our system while it's waiting for processing or delivery. Once delivered to the destination, the data is purged. This interstitial storage is in place to make sure your data is delivered successfully, even if the downstream destination is unavailable.

What happens if a Tarsal flow fails?

Tarsal checkpoints from the last successful sync of data, such that if source or destination goes down, the system knows where to resume once the failing connector comes back online. This means no data will be lost when a flow fails, but that also means that no data will be added or updated in the destination during this time.

During this time, the following will happen:

• The flow status of the flow is set to "Error."
• If notifications are configured in your account, notifications will be sent immediately (and re-sent periodically).
• If a source API is down, Tarsal will retry polling at the sync frequency set by the user until the API comes back online.
• If a destination goes down, logs will be retried with exponential backoff and jitter. If an error goes down for user-related errors (like authentication failure, destination deleted, etc), the system will continue to send notifications and queue data until the issue is resolved. For help resolving failing connectors, feel free to contact us via the support portal at https://support.tarsal.cloud for help with resolving failures.

Once the issue that caused the flow to fail is resolved, Tarsal automatically resumes your flow from where it left off.

Tarsal has relationships with vendors to stay up to date of API changes. However, in the event a flow fails because of an unannounced vendor API change, Tarsal is also notified and will research and make the appropriate changes. Once the updates are deployed, the system will pick up where it left off. No intervention is needed on your end.

Does my data change?

Many sources provider their data in JSON format. A disadvantage of JSON is that it does not natively support value types of float or integer - both are provided as a type number. In these cases, Tarsal may modify the value type to be one of integer or float instead of number. If this is the case, you will see a Data Type Mappings table in the documentation.

Data Type Mappings