> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useparagon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring Syncs

> Review Managed Sync lifecycle, warning, error, and webhook delivery logs in Event Logs.

Managed Sync emits [Event Logs](/monitoring/event-logs) as Syncs run, retry, complete, or fail. These logs help you understand what happened inside Paragon when a Sync changes state, encounters a recoverable integration issue, enters an errored state, or cannot deliver a webhook to your app.

Event Logs complement [Managed Sync Webhooks](/managed-sync/webhooks):

* **Webhooks** notify your application when records change or a Sync needs application-level handling.
* **Event Logs** give your team an operational timeline for debugging and support.

## Viewing Managed Sync Logs

To view Managed Sync logs in the dashboard:

1. Open your Paragon project.
2. Navigate to **Monitoring**.
3. Select **All Logs**.
4. Filter **Type** to **Managed Sync**.

You can further narrow the view with **User ID**, **Integration ID**, **Trace ID**, and **Timestamp** filters. You can also search the log payload for values like a Sync ID, pipeline name, or record ID.

## Log Details

Expanding a Managed Sync log shows the full event context. Common properties include:

| Property      | Description                                                                                                                                   |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| `syncId`      | The Sync ID returned by the Sync API. This is the same value shown as `syncInstanceId` in Managed Sync webhook payloads.                      |
| `traceId`     | Groups logs from the same Sync iteration, such as one initial sync, incremental sync, or periodic full sync run.                              |
| `userId`      | The Connected User associated with the Sync.                                                                                                  |
| `integration` | The integration associated with the Sync.                                                                                                     |
| `pipeline`    | The Managed Sync pipeline, such as `files`, `contacts`, or `tickets`.                                                                         |
| `syncEvent`   | The specific Managed Sync event, such as `INITIAL_SYNC_COMPLETED`, `SYNC_RUN_RATE_LIMITED`, or `SYNC_RUN_ERROR`.                              |
| `syncType`    | The Sync lifecycle phase: `INITIAL`, `INCREMENTAL`, `FULL`, `PERMISSION`, or `SINGLE_RECORD`.                                                 |
| `syncStatus`  | The Sync status at the time of the log, such as `ACTIVE`, `IDLE`, `RATE_LIMITED`, or `ERRORED`.                                               |
| `summary`     | Completion counts for successful Sync runs, including created, updated, deleted, total processed, total changes, and duration when available. |
| `error`       | Error context for warning and error logs, including recoverability, HTTP status, error code, and retry metadata when available.               |

```json Example Managed Sync log context expandable theme={null}
{
  "type": "Managed Sync",
  "message": "Incremental sync completed",
  "traceId": "0197a7a4-68c3-7b4f-9f4e-727b1fbf15a0",
  "logContext": {
    "syncId": "163a345e-2dd4-51ff-bcf5-7667de564bb0",
    "userId": "user_01JH448D13EX2BE1SC1GXVT05R",
    "integration": "googledrive",
    "pipeline": "files",
    "syncEvent": "INCREMENTAL_SYNC_COMPLETED",
    "syncType": "INCREMENTAL",
    "syncStatus": "IDLE",
    "summary": {
      "recordsCreated": 2,
      "recordsUpdated": 5,
      "totalChanges": 7,
      "durationMs": 18342
    }
  }
}
```

## Log Types

### Lifecycle Logs

Lifecycle logs show when each Sync phase starts and completes:

* `INITIAL_SYNC_STARTED` and `INITIAL_SYNC_COMPLETED`
* `INCREMENTAL_SYNC_STARTED` and `INCREMENTAL_SYNC_COMPLETED`
* `FULL_SYNC_STARTED` and `FULL_SYNC_COMPLETED`

Use lifecycle logs to confirm that a Sync is progressing, identify how long a Sync run took, and inspect how many records were created, updated, or deleted in a completed run.

### Warning and Retry Logs

Managed Sync automatically retries recoverable failures, including rate limits, timeouts, and temporary integration API errors. These appear as warning-level logs, such as:

* `SYNC_RUN_RATE_LIMITED`
* `SYNC_RUN_WARNING`
* `FULL_SYNC_INTERRUPTED`

Warning logs include `error.recoverability: "RECOVERABLE"` and may include retry details such as `backoffMs`, `nextRetryAt`, `attempt`, and `maxAttempts`.

<Info>
  Rate limits and temporary upstream failures usually do not require application changes. Use these logs to understand delays or repeated retries for a specific Sync, Connected User, or integration.
</Info>

### Error Logs

Error-level logs indicate that a Sync could not continue without intervention. Managed Sync emits error logs for cases such as invalid Sync configuration, duplicate Sync creation, authentication failures, or terminal integration errors.

Common error events include:

* `SYNC_CREATION_FAILED`
* `SYNC_RUN_ERROR`

When a Sync enters an errored state, check the log's `error.errorCode`, `error.httpStatus`, and `error.recoverability` fields. After resolving the underlying issue, you can [re-enable the Sync](/managed-sync/api/reenable-sync).

### Webhook Delivery Logs

Managed Sync emits `SYNC_WEBHOOK_FAILED` when Paragon cannot deliver a Sync webhook to your configured webhook URL. The log is warning-level while Paragon will retry delivery and error-level after retries are exhausted.

Use this event to debug endpoint availability, response status codes, timeouts, and webhook retry behavior. See [Managed Sync webhooks](/managed-sync/webhooks) for webhook configuration and payload details.