Configuring archive break records for Pullup jobs

October 8, 2026

This topic shows you how to configure archive break records to send details of breaking records from Pullup jobs to your data source. Enabling this feature allows you to automatically store row-level data for failed quality checks directly in your database.

You can configure the storage location at the connection level to align with your organization's data architecture.

Prerequisites

To archive break records, you need the following permissions and configurations:

Requirement	Details
Collibra permissions	To configure your connection, you have a global role with the Data Quality > Manage Data Sources global permission. To view and download break records, you have Preview Rule Break Records resource permission.
Existing PostgreSQL connection and Data Quality Pullup Processing capability	You have an established connection to a PostgreSQL data source. The Data Quality Pullup Processing capability enabled on your connection is already configured on the same Edge site. Important Each Data Quality Pullup Processing capability requires a separate PostgreSQL connection, even when multiple capabilities share the same physical database. Create one PostgreSQL connection per Data Quality Pullup Processing capability where you want to archive break records. For more information on Pullup-compatible connections, go to Supported data sources for Data Quality & Observability.
Data source privileges for break records	Because exact permission models vary significantly across different data platforms, consult your organization's database administrator to provision the exact permissions. The service account connecting to your data source requires the following generalized privileges: On the source data (to monitor records): Read access (SELECT) on the specific tables and views you intend to monitor. On the destination schema (to archive break records): Create access (CREATE TABLE and CREATE VIEW) in the designated archive schema. Note You only need create access once per break records table, or you can create it manually with explicit update access. All monitors write to the same break records table, so create access can be safely revoked after initial setup. If the break records storage location changes, create access is required again to generate a new table. Modify access (ALTER TABLE and ALTER VIEW) to update schema structures, such as adding new columns. Drop access (DROP VIEW) to clean up or replace views as needed. Read access (SELECT) on the newly created tables and views. Write/edit access (INSERT, UPDATE, and DELETE) on those created tables to actively manage the archived records over time.

Enabling archive break records

Important Ensure that the service account used for the connection has all the privileges listed above. If any privilege is missing, the system cannot archive break records.

1. On the main toolbar, click → Settings.
   The Settings page opens.
2. In the tab pane, click Edge.
   The Sites tab opens and shows a table with an overview of your sites.
3. In the site overview, click the name of the site where the Pullup connection is configured.
   The site page appears.
4. Click the Capabilities tab.
5. Click the Data Quality Pullup Processing capability where you want to archive break records.
6. Set Archive Break Records Connection to your desired archive destination.

Note As of Collibra 2026.10, only PostgreSQL is available as an archive destination.

7. Click Save.
8. On the main toolbar, click → Data Quality.
   Data Quality & Observability opens.
9. Click Connections.
   The Connections page opens.
10. Open your desired Pullup connection.
11. Click the Archive break records switch to enable archive break records.
12. Select the destination database and schema from the drop-down menus, where break records will be written.

    Note The database and schema must already exist in your connection.

13. Create and run a Pullup job on this connection.
14. Create a rule that will return breaking records.
15. Re-run your job.
    When breaking records occur, Collibra writes them to the database you selected in step 12.

Helpful resources

• Configuring archive break records for Pushdown jobs
• Add or edit a custom SQL rule