# Pipeline sync management guide

> After configuring a pipeline, you can manage how and when data is synced, review the status of regular syncs, and troubleshoot issues as needed.

> **Note:**
> To configure pipelines for data ingestion into Rippling, your company must subscribe to Rippling AI.

## Overview

Data you bring into Rippling using pipelines is synced regularly so it stays up to date with changes in the source system. After configuring a pipeline, you can manage how and when data is synced, review the status of regular syncs, and troubleshoot issues as needed.

## Sync types

There are two types of syncs: **incremental** and **full**.

### Incremental sync

An incremental sync checks for recent changes (new records, updates to existing records, deleted records) and updates the data in Rippling accordingly.

By default, incremental syncs occur on an hourly basis for all pipelines, but you can change this to your preferred frequency.

### Full sync

A full sync is a full refresh/replacement of the data. The purpose of a full sync is to capture any changes that were missed in incremental syncs to ensure the data in Rippling exactly matches what’s in the data source. For example, when a record is deleted in the source system, an incremental sync may miss this if the source system doesn’t pass an indicator to Rippling, or if the indicator is dropped before the next scheduled incremental sync.

Because a full sync refreshes every record, it typically takes longer than an incremental sync. You can schedule full syncs to occur on your preferred cadence (for example, after business hours) so they don’t disrupt your operations.

## Change the incremental sync schedule

> **Note:**
> This option is not available for data warehouse (zero ETL) connections. Because these connections are live and do not import data into Rippling, syncs are not necessary.

To change the incremental sync schedule, follow these steps:

1.  From the sidebar, select **Data** > **Pipelines**.
2.  Click on the pipeline for which you want to configure a schedule.
3.  Click the circle arrow icon in the header and select **Create sync schedule**.
4.  A window opens where you can select your preferred sync frequency:
    -   Every 15 minutes
    -   Every 30 minutes
    -   Every 4 hours
    -   Every 6 hours
    -   Every 8 hours
    -   Every 24 hours
5.  Click **Save**.

The schedule is saved. Incremental syncs will now run on the designated schedule.

## Schedule full syncs

You can schedule full syncs to occur on your preferred cadence. Any full syncs you configure will be in addition to incremental syncs.

> **Note:**
> This option is not available for data warehouse (zero ETL) connections. Because these connections are live and do not import data into Rippling, syncs are not necessary.

To set up a sync schedule, follow these steps:

1.  From the sidebar, select **Data** > **Pipelines**.
2.  Click on the pipeline for which you want to schedule the sync.
3.  Click on the three dots in the top right corner and select **Full sync**.
4.  A window opens where you can configure the following schedule settings:
    -   **Enable schedule.** By default, this is switched on. If you want to disable the schedule, switch it off.
    -   **Frequency.** Select the frequency for the sync: hourly, daily, weekly, or monthly.
    -   **Time.** Select the time of day when you want the sync to occur.
    -   **Time zone.** Select the time zone for the sync time.
    -   **Streams.** Select the streams you want to include in the sync. Items you do not select will not be included in the full sync, but they will still be included in incremental syncs.
5.  Click **Create schedule**.

The schedule is saved and will be run at the designated time.

## View the next scheduled sync

To see the date and time of the next scheduled sync, click on the pipeline and review the **Next scheduled run** in the header.

## View sync history

To view a pipeline’s sync history, follow these steps:

1.  From the sidebar, select **Data** > **Pipelines**.
2.  Click on the desired pipeline and select the **Sync history** tab.

The sync history is shown on the left. Each sync displays the date and time it ran and the status of the sync. You can scroll through the sync history or use the **filter** icon to filter the list by date, status, or sync type.

Following are the possible sync statuses.

| Sync status | Description |
| --- | --- |
| In progress | The pipeline’s initial sync is in progress. |
| Preparing for AI | The initial sync has completed and the data is being indexed for use by Rippling AI. Note that responses to Rippling AI queries may be based on partial data until this step is complete. |
| Pending | The sync is scheduled but has not yet started. |
| Sync in progress | The sync is currently in progress. |
| Success | All fields were successfully discovered and 100% of extracted records were written to the object without issue. |
| Warning | The sync completed, but some issues were encountered. This status appears when records were partially written (for example, when an invalid field value was set to null and the record was still loaded), or when fewer than 10% of records were dropped. |
| Failed | The sync encountered critical errors that prevented it from completing successfully. This includes errors that stop extraction (such as service, system, or authentication failures), or cases where 10% or more of records were dropped. |
| Cancelled | The sync was cancelled before it completed. |

### Review sync details

Click on any sync, and its details will be displayed on the right side of the screen. You can choose to view the details by destination object or by error type.

When viewing by destination, the **Sync status** column shows the status of the sync for each object.

When a sync fails, there are three types of errors you will see here.

| Status | Description | Resolution |
| --- | --- | --- |
| Authentication error | Rippling was unable to authenticate to the third-party data source to complete the sync. | Check your authentication credentials to confirm they are still valid. Sometimes keys expire, rotate, or get revoked. The key could also be incorrect or mistyped. To update your credentials, open the pipeline’s details, then click the three dots in the top right corner and select **Update credentials**. |
| Service error | There was a problem with the third-party data source that caused the sync to fail. | Check that the source system is operational. Confirm your credentials have the required permissions. Confirm you have not exceeded a rate limit imposed by the third-party source. See the third-party app’s API documentation for details about any possible rate limits. |
| System error | There was a problem in Rippling that caused the sync to fail. | The issue may be temporary. Retry the sync to see if it resolves. Contact Rippling Support if the error persists. |

## Pause syncing

You can pause a pipeline at any time to temporarily cease importing/syncing data. Pausing lets you put data syncing on hold without deleting your setup. This can be useful when you want to change your setup or fix an issue with a stream, and you want to stop syncing while you make your changes.

To pause a pipeline, click the **pause** icon at the top of the page.

You’ll see a confirmation message letting you know all data streams will stop until you resume, and that data will not be updated during the pause. Click **Pause all data streams** to confirm.

In custom pipelines, you can also pause a specific stream. From the **Destinations** tab, find the stream you want to pause, then click the three dots in the _Actions_ column and select **Pause syncing**.

## See also

-   [Get started with pipelines](https://developer.rippling.com/documentation/rippling-platform/pipelines/getting-started)
-   [Set up a custom pipeline](https://developer.rippling.com/documentation/rippling-platform/pipelines/custom-pipeline-setup)
-   [Pipeline FAQs](https://developer.rippling.com/documentation/rippling-platform/pipelines/faqs)
-   [Review data lineage across Rippling](https://developer.rippling.com/documentation/rippling-platform/data-model/data-lineage)

Source: https://developer.rippling.com/documentation/rippling-platform/pipelines/sync-management

> For the complete documentation index, see [llms.txt](https://developer.rippling.com/llms.txt). Public pages have a Markdown version at the same URL with .md added.
