Skip to main content
Run history is the operational record for a pipeline. Use it to confirm:
  • run status
  • row counts
  • duration
  • delivery targets
  • no-primary-key warnings
  • error messages

​
Run states

Typical states include queued, pending, running, succeeded, failed, and waiting. Runs can wait when worker capacity or disk budget checks delay execution.

​
What to inspect after a run

  1. Confirm the run succeeded.
  2. Confirm rows were written to the intended schema.table.
  3. Check for no-primary-key warnings.
  4. Compare the destination table shape against the SQL model output.
  5. Review the error message if the run failed.
MantrixFlow sanitizes credential-like values in errors and does not return connection secrets in run output.