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

# Replication monitoring

> Track sync status, monitor data freshness, and troubleshoot replication issues

The Prequel Import Destination specs specify detailed error codes on a per row/record level. This enables granular debugging at both the individual transfer level, but also one level deeper at the row level.

## Monitoring in the Admin UI

All sync issues are raised in the Prequel Import Admin UI, and can be drilled down into the individual rows.

<Note>
  Because Prequel Import does not persist pipeline data in the application database, some granular queries may take longer to complete while details are retrieved from the Datalake cache.
</Note>

## Monitoring synchronously

For live error detection, Prequel Import emits webhooks for most application events. These webhooks can be delivered to a variety of monitoring platforms including Slack, PagerDuty, Datadog, and more.

See the [Webhooks and Monitoring](/import/logging/webhooks-and-monitoring) guide for details.

## Cancelling in-flight jobs

Running extracts and loads can be cancelled via the API:

| Method | Path                           | Purpose                                                         |
| ------ | ------------------------------ | --------------------------------------------------------------- |
| `POST` | `/import/extracts/{id}/cancel` | Cancel a running extract. Returns the updated extract resource. |
| `POST` | `/import/loads/{id}/cancel`    | Cancel a running load. Returns the updated load resource.       |

Cancellation is best-effort. A job that has already reached a terminal state will be returned unchanged.

## Provider-facing monitoring

All monitoring data is designed to be securely displayed to Providers in embedded experiences.

See the [Customer Experience](/import/getting-started/customer-experience) guide for details.