Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

download

Data Sync Run History

After a manual or scheduled data sync is run, information about the sync is accessible from the Run History button, regardless of whether or not the data sync was successful. You can view and interact with the data sync run history to monitor the progress or status of the sync and any errors generated if the sync was unsuccessful.



The Run History list displays the following information.

Column

Description

Search

Allows to find a specific record by entering its pipeline ID in the search field. For more advanced search options, use additional filters and logic. For more information, see Filtering Records in the Grid View.

Pipeline ID

The ID of a sync operation. Click the link to view object-level details like the entity name, current processing stage, status, batch item count, successful items, failed items, and the total number of source records. You can also download an error report in a JSON file by clicking the Errors button from the Pipeline ID > Run Details screen.

Start Date and Time

The date and time the sync operation was initiated. You can use the start date to get an understanding of how recently data was pulled from Salesforce to the consumer service.

End Date and Time

The date and time the sync operation was completed or failed.

Sync Status

  • In Progress - The data sync operation is currently in progress.
  • Success - The data sync operation was successful without any errors.
  • Failure - The data sync operation failed with one or more errors.
  • Retry - The data sync operation was interrupted.
Note:

For reverse data sync, the status will remain "In Progress" until all parent and related child objects are fully synced to Salesforce.

Action

  • Retry: If the sync fails for any reason, you can retry the sync after clearing the issues.

    Note:

    The system hides the Retry action for pipelines with a Failure sync status that are in the Fetch or Transform stages, preventing unnecessary retries during intermediate processing. Additionally, after one retry attempt, if a batch with a Failure sync status fails again, the system does not allow further retries.

  • Cancel: You can cancel data sync operations that are currently in progress, giving you more control over your sync processes and saving time when a sync takes too long or was started by mistake.

    Cancellation is supported for operations that meet all of the following criteria:

    • Trigger Type is not Schedule

    • Sync Direction is ETL

    • Sync Type is either Full or Incremental

    • Sync Status is In Progress

      Note:

      Canceling a data sync is a critical action. The outcome varies depending on the stage of the sync at the time of cancellation, so proceed with caution.

      Behavior by Sync Stage:

      • Fetch stage:

        • Operation is terminated safely.

        • No partial data sync occurs.

      • Transform stage:

        • Operation is terminated safely.

        • No partial data sync occurs.

      • Upload stage:

        • Operation is terminated safely.

        • Partial data sync may occur, so use caution when canceling at this stage.

Trigger Type

Indicates whether the sync was Scheduled, Manual, or Resync.

Run Type

Indicates the mode in which the data sync was initiated. The application supports the following modes:

  • Incremental: Synchronizes only new or changed records.
  • Full: Synchronizes all records from the beginning.
  • Retry: Re-triggers synchronization for failed records at a later time. This will be enabled for failed status.
  • Attribute: Used for syncing master data, such as product attribute metadata.
  • ABO: Used for syncing asset attribute-based transactions.
Note:

The Attribute and ABO options are available only during full, incremental, or scheduled sync operations.

Current Stage

The current status of the Data Sync.