Sync Logs and Run History

This page is the authoritative reference for what appears in ETL sync history and run details. All of this is visible on the integration Status tab.

Sync List (Status Tab)

For each integration, the Status tab lists all syncs that have run:

• In progress: Indication when a sync is currently running.
• Per sync: Start time, end time, duration; number of tables; volume (records moved); emitted records and committed records; status (successful, failed, completed with errors).

Clicking a sync expands or opens per-table details for that run: emitted/committed and duration per table.

Sync Status

• Successful: Sync completed without errors; data was written to the destination as expected.
• Failed: Sync did not complete (e.g. connection error, permission error). No data or partial data may have been written.
• Completed with errors: Sync finished but some tables or rows failed. Check per-table or run details for which part failed.
• Aborted: Sync was manually stopped by user.

Emitted and Committed Records

• Emitted records: Count of records that left the source and were processed by Matia for this sync (or per table).
• Committed records: Count of records that were successfully written and confirmed in the destination (or per table).

A delta between emitted and committed is normal when Matia applies transformations, flattening, or normalization. Large or unexpected deltas may indicate filtering, deduplication, or errors; use the Status tab and any error messages to investigate.

Per-Table Details

When you drill into a sync run, you see per table:

• Emitted and committed counts
• Start time, end time, duration for that table

Use this to see which table drove volume or caused a failure.

Changelog

The Changelog tab on the integration is an audit log of configuration and state changes (not sync runs). Each entry: what changed, when, and which user made the change. Examples: enable/disable, schema changes, settings updates.

For sync mode definitions, see Sync modes. For trigger and schedule, see Create and configure an ETL integration.