Export Runs

Export Runs is the execution history — one record per pipeline run, showing start/end time, row counts and success or failure. It is the monitoring and audit surface that confirms the warehouse is fresh and helps diagnose any failed load. Reliable run history is essential for trustworthy BI reporting.

Export Runs
Export Runs — live screen from the BridgeERP MFI Suite.

Workflow

  1. Open Export Runs to view the run history.
  2. Filter by pipeline or date to find a specific load.
  3. Open a run to inspect rows exported, duration and status.
  4. Investigate the error detail on any failed run.
  5. Re-trigger the pipeline once the issue is resolved.

Fields reference

Every field on this screen, drawn from the live data model.

FieldTypeRequiredDescription
Pipeline
pipeline_id
Link → mfi.dw.pipelineYesPipeline
Destination
destination_id
Link → mfi.dw.destination—Destination
Provider
provider
Choice: Google BigQuery, Snowflake, Amazon Redshift, Amazon S3 (Parquet), SFTP (CSV gzip), Generic HTTP POST—Provider
Run Started
run_started
Date & time—Run Started
Run Ended
run_ended
Date & time—Run Ended
Duration S
duration_s
Decimal—Duration S
State
state
Choice: Running, Success, Failed, Partial—State
Rows Exported
rows_exported
Number—Rows Exported
Bytes Out
bytes_out
Number—Bytes Out
Watermark Old
watermark_old
Text—Watermark Old
Watermark New
watermark_new
Text—Watermark New
Columns (JSON)
columns_json
Long text—Columns (JSON)
Error Message
error_message
Text—Error Message
Lineage
lineage_ids
List—Lineage

Status lifecycle

Records on this screen move through these statuses:

Running → Success → Failed → Partial

Notes & rules

  • Model mfi.dw.export.run; one record per pipeline execution.
  • Captures start/end time, row counts and success/failed status.
  • Holds error detail for diagnosing load failures.
  • Confirms warehouse freshness for downstream BI dashboards.

Technical model: mfi.dw.export.run · Record: Data Warehouse Export Run

Was this page helpful?